Then he concludes that 600nits is unnecessary and that he doesn't need or want the USB-C ports.
I have no idea why he went with the apple display instead of any good 4k screen for 400$, or two of them.
2,222 karma · joined September 23, 2012
Then he concludes that 600nits is unnecessary and that he doesn't need or want the USB-C ports.
I have no idea why he went with the apple display instead of any good 4k screen for 400$, or two of them.
I wrote a few in Lua, but it still felt second class citizen to built-in C dissectors, loading them was annoying and the UI to use them was too.
A good dissector will annotate fields with semantic meaning and group and nest them, giving wireshark the precise bit offset+length where a value came from.
Those are some different requirements than other parsers and reuse is therefore a bit difficult.
I get why samsung doesn't want to get sucked into this. It does suck though, at least the ISO should work.
In my personal opinion he lacks experience with actual development and skill to even talk about code, let alone good development practices. He is a book author, not a developer sharing his expertise.
He spouts hot air for money.
FlightRecorder, single jar deployables, the JDK cli utils to get stacktraces and heap dumps etc are good.
No npm getting a zillion files. Just get some jvm, point it at your jar and done.
If you are talking 2001 servlet container and so on, sure terrible, but if you are running those, switch jobs, thats not java's fault.
The numbers might not be referring to the ukraine conflict.
I and many other, probably mistakenly, believed this would keep putin in check. You have to remember that for the US russia is far away, but for us it's a neighbor and our history is bound together for centuries. East germany was part of the soviet union for decades.
We live, lived, in the longest stretch of peace on the european continent and maybe it was NATO and a common enemy but it was also because of diplomancy, compromise and economic integration.
The US is also importing $25bn of crude oil from russia while telling germany to cut down on gas imports from a reliable parter at that point.
https://www.eia.gov/dnav/pet/hist/LeafHandler.ashx?n=PET&s=M...
Putin is a whacko, damn.
Code being predictable is a huge win, not only with other people but also with your own code from 10months ago.
It also makes change more calculable.
I feel like they are chasing a aesthetic of conciseness, their perfect little haskell program, not recognizing that regularity and good api design are much more important.
What is beautiful for a 100loc program becomes ugly and wrong for a 100kloc program. Other aspects become much more important.
I'm not a huge fan of go, but it proved there is a necessity for boringness in cooperation.
Boring syntax does not mean the upper limit is mediocrity, saying that is revealing shallowness.
Before that happens Apple's privacy campaign is just a lot of hot air.
Pulls in two pretty huge dependencies though, electron and pandoc.
But yes, the default is autocalibration. But honestly, the difference isn't that bad, it's probably like 100ppm offset for stale room air from outside, and 100 doesn't make a huge difference when you are trying to measure around 1500.
Had n-ary nodes though, the nice thing is that the proof is equal to the path to the node in that case (well because of radix/trie).
Was always playing with the idea of writing it down especially with all the crypto bullshit going on, but I was too lazy.
Is 8.3.1 patched?
I'm joking of course, but the platform support list of rust is pretty good looking at [1].
I'm pretty sure people developing for arm5 aren't building the linux kernel on arm5.
[1] https://doc.rust-lang.org/nightly/rustc/platform-support.htm...
My first judgement was that it seemed a bit rehearsed, but I ended up really enjoying the style. It felt very respectful of my time as a viewer, very concise and well prepared. I'm sure a lot of time went into that and I appreciate it.
So thanks, for both an awesome application of rust and an amazing presentation.
tf-idf and phrase search alone make lucene 10x better, not speaking of the compression, fuzzy search, advanced query features etc.
I love new search engines like tantivy etc, but this is, due to the tone, a sad joke.
x32-glibc is about 10% faster than amd64-glibc, but surprisingly x32-musl is 40% slower than the glibc time.
Author mentions that it might just be stdout buffering, implicitly done by glibc but not by musl hinted at by 54min of kernel time vs 7min with glibc.
I'm actually more interested in memory usage.
It's not that simple.