HN user
Software engineer in Trondheim, Norway.
https://github.com/mpolden
I put my personal site behind Cloudflare last year specifically to combat AI bots. It's very effective, but I hate that the web has devolved to a state where using a service like Cloudflare is practically no longer optional.
https://github.com/darkreader/darkreader is great for this. Adds dark mode to any site.
OpenJDK 17 is in Debian 11 as well [0]. A decision was made to include it before its official release since the release is so close (September). An updated package will be available when it's released.
From the release notes [1]:
Debian bullseye comes with an early access version of OpenJDK 17 (the next expected OpenJDK LTS version after OpenJDK 11), to avoid the rather tedious bootstrap process. The plan is for OpenJDK 17 to receive an update in bullseye to the final upstream release announced for October 2021, followed by security updates on a best effort basis, but users should not expect to see updates for every quarterly upstream security update.
[0] https://packages.debian.org/source/testing/openjdk-17
[1] https://www.debian.org/releases/bullseye/amd64/release-notes...
Records were introduced in Java 14 [1]. An immutable DTO, with minimal boilerplate, that still behaves a class. Example:
record Point(int x, int y) {}
[1] https://blogs.oracle.com/javamagazine/records-come-to-java
There are multiple LSP clients though, there's lsp-mode [1] and eglot [2].
After trying out both, I prefer Eglot, mainly because I find it faster and less intrusive than lsp-mode. It also composes better with built-in packages, such as flymake . I use gopls and pyls as language servers.
Syncthing is a great piece of software. I configured it on three of my machines in March and I've had zero issues since. In fact, it has worked so well that I don't even think about it.
One of the machines even runs an old version found in Debian stable repos, but there has been no issues syncing with machines running newer versions.
Only downside for me is that there's no iOS client.
Norwegian here. 20 days a year is the legal minimum, while 25 days is the norm. I get 30 days a year while working for an American company, which is a bit ironic.
Not surprised by these bugs any more.
The sheer amount of bugs in High Sierra is ridiculous, with the exception of the root password bug, I've personally experienced the following bugs with my Thunderbolt display:
* In 10.13 or 10.13.1 the built-in web camera was broken. The video would freeze after a few seconds when attempting to use the camera in FaceTime. This was fixed in 10.13.2.
* In 10.13.2 USB audio devices connected to the TB display no longer work properly. After playing audio through the device (USB DAC in my case) for 30-60 seconds, some sort of interference/electrical noise appears for 5-10 seconds every minute or so. I assume this has something to with "Improves compatibility with certain third-party USB audio devices." from the 10.13.2 release notes.
This support article explains how to disable the root user: https://support.apple.com/en-us/HT204012
And this is likely the reason for the reportedly low sales of the 8. I was surprised when they announced both at the fall event as it seemed obvious the X would cannibalize sales of the 8.
The iPhone is already a expensive premium phone, why bother with incremental changes of the 8 when the cool and shiny X is right around the corner.
It's also strange to me how they offer two new phones with different feature sets. Usually when Apple introduces a new device with a controversial change (e.g. USB-C only on the 2016 MacBook Pro), they don't offer a updated device without that change. It can be perceived as a lack of faith in the new product.
Outside of general purpose libraries that are found in most software projects it's not based on any existing software. It's built from the ground up by Oath, and the companies that preceded it: Yahoo, FAST, Overture since early-mid 2000s.
This article has some more details about the history: https://www.cnbc.com/2017/09/26/yahoo-open-sources-vespa-for...
Disclamer: I work on the Vespa team in Trondheim, Norway.
The serving and admin/config layers are Java, while the content cluster is C++. Please see the architecture diagram on http://vespa.ai/.
Maybe this can be merged with the discussion from yesterday: https://news.ycombinator.com/item?id=15339851
Bad example. You can do this in Java 8: java.nio.file.Files.readAllLines(path) which returns List<String>.
Uber remains illegal in Norway as all taxi drivers need a permit granted by the government. The subject is under heavy debate though.
Another anecdote: My sister took over my apartment late 2014. Some time in 2015, the dishwasher (Miele) stopped working. She called support to see if it could be repaired. When she provided them with the serial number she was told that the dishwasher was in fact manufactured in 1994.
It had lasted through 21 years of regular use, by multiple owners.
Pretty much the same ones are missing on Norwegian Netflix as well.
Ars Technica has written a detailed review [0], there's some things on the networking side related to IPv6 and ECN, but that's pretty much it. APFS preview is interesting, but not really stable/usable yet from what I understand.
[0] http://arstechnica.com/apple/2016/09/macos-10-12-sierra-the-...
You should also read James Mickens' USENIX articles if you haven't: http://mickens.seas.harvard.edu/wisdom-james-mickens
The humour and tone is similar to the "Programming Sucks" article. I recommend starting with "The Night Watch".
This is not entirely accurate. The way these DNS services work is that they return a different IP address (one they control) for certain Netflix domains. Then they do TCP proxying between you and Netflix to get around the region restrictions.
Previous discussion: https://news.ycombinator.com/item?id=10771100 (different URL, but looks like it's the same article)
Previous discussion: https://news.ycombinator.com/item?id=9190955
Even if Apple uses high quality components that fail less frequently, it's still computer hardware at the end of the day. Hardware fails, no matter how much QA you do, so #2 is never moot.
Experienced bad memory on a MBP Retina (late 2013) recently, it was purchased in December 2013. You can't swap out the memory because it's soldered to the motherboard, so the entire motherboard has to be ordered from Apple and replaced.
This wouldn't be so bad if you could easily move the SSD to a new Mac, but that's not an option either.
I always use go-flags [1] in my Go programs. It has support for GNU-style options, pretty help output, subcommands, automatic parsing of more complex arguments (e.g. time.Duration) among other things.
I do wish they would improve the included flags package though. There are lots of nice third party packages, but having a proper one in the standard library would've been better.
I haven't tried that one. I'm using asuswrt-merlin [0], which is another fork based on the official Asus sources.
It's very similar to the original firmware, but with a few extra bug fixes and features. Asus occasionally backports some of the bug fixes to the official firmware. The vulnerable feature has been disabled in the latest version. [1]
[0] https://github.com/RMerl/asuswrt-merlin
[1] http://forums.smallnetbuilder.com/showthread.php?t=21774
I've found that https://github.com/jmoiron/sqlx (mentioned in the slides) works very well for SQL and mapping values to structs in Go. It's not an ORM though. You still write plain parameterized SQL queries, but mapping results to structs is very elegant.
The mapping process is very similar to how other packages in Go work (e.g. encoding/json), so if you already know Go it feels very natural.
There has been some controversy around DD-WRT and GPL, maybe that's why.
http://web.archive.org/web/20070726045835/http://www.bitsum....
Still seems like a lot, 2 billion a week is over 3300 every second. Says a lot about the scale at which Google operates.
Seems to be down. Google Cache: https://webcache.googleusercontent.com/search?q=cache:TfWANJ...
LTS releases rarely introduce huge changes, they just focus on increasing stability and polishing features from the preceeding non-LTS releases.