Hacker Newsnew | past | comments | ask | show | jobs | submit | more btym's commentslogin

Are you worried about your chip and OS today?

Yes, Intel is still pulling these stunts and there are not many viable alternatives.


> there's no evidence that DVORAK is better than QWERTY

Here's my go-to reference: http://mkweb.bcgsc.ca/carpalx/?keyboard_layouts



This is worth reading. Someone made a serious effort to quantify differences in effort and strain between keyboard layouts. Thanks for sharing the link!



> Docker takes about 10m to build: https://jenkins.dockerproject.org/job/docker/job/docker.gith....

That seems to be docker.github.io, the Docker documentation, not Docker itself (and not written in Go).


Doesn't sound too fast, that's about how long it takes for FreeBSD kernel to be compiled[1] and I would imagine a kernel is more complex. The whole system takes about 50 minutes[2]

[1] https://ci.freebsd.org/job/FreeBSD-head-amd64-LINT/buildTime...

[2] https://ci.freebsd.org/job/FreeBSD-head-amd64-build/buildTim...


Go's main compilation performance gains come from incremental compilation. Since C++ doesn't have real module support merely parsing the entire dependency graph from headers can take a very long time. In go if you have .a pkgs for all your dependencies your program will compile very fast.

If you use docker as part of your ci build the dependencies as a separate step so they can be cached between builds. This is especially important for libraries like sqlite, which can take a lot longer to compile.


On a not-too-old notebook, building k8s needs less than one minute.


Nim by Example[0] is a great introduction. The blog mentioned in the OP also has a writeup that explores some of the tooling[1]. After that, the official tutorial[2] is a comprehensive dive. The standard library documentation is sometimes lacking but is easily searchable.

[0]: https://nim-by-example.github.io

[1]: http://howistart.org/posts/nim/1/

[2]: https://nim-lang.org/docs/tut1.html


Second this. I've been playing with Nim for the past couple months and love it. The biggest downside has been lack of tooling.


>EVERY OTHER CONNECTOR has gone through improvements. new USB standards. new video. everything. why is this any different?

Physical improvements have been necessary for USB to increase bandwidth. 3.5mm is a connector for carrying two (sometimes 3) analog signals, and backwards-incompatible changes aren't necessary until we develop a third ear.


No, overall, you'll be using more power (DAC vs encoding + decoding + DAC). It's just split across two devices you have to charge independently.


Sure, but battery power in the phone is valuable. Modern Bluetooth headphones can play 30-40 hours of music per charge.


Hi, member of the vast majority of people here. I don't want to have to carry a dongle.


>Assuming this is how much time it takes to initialize the VM

Why would you assume that?


"How Python does Unicode: Poorly."


Python 2 maybe. Python 3 does Unicode wonderfully well; I miss it whenever I'm working with other languages.


All Python 3 did was put a hard barrier between bytes and strings. That's it.

Mising is all the grapheme handling that languages that do Unicode strings right have.


I'd be curious to hear why you think that.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: