Lorkki

I'm not sure how that follows. Most big open-source projects are in practice owned and controlled by a single company/entity, and the processes don't differ much from what you'd see in-house. What you're describing sounds more like how standardisation bodies work than the realities of functioning software projects.

I wouldn't know at first glance what radare2 does, so this title was actually slightly more informative. Still nice to hear that it builds on previous work, though.

Also, I believe the statistic of interest here is incidents per operating hour, not per flight?

> tietokone = knowledge machine (literally) = computer

This is somewhat beside the point, but although in everyday speech "tieto" usually means knowledge in the sense of knowing a fact or skill, it can also be taken as "information", which seems more likely to have been the original intent of the term.

Nevertheless, pretty much every elementary computing course in Finnish begins by stating that "the computer doesn't actually know anything". :)

Both type inference and borrow checking have also received a whole bunch of small improvements over the past couple years. Subtle enough that you probably wouldn't notice them except in that the language just takes less effort to use.

If you use Rust 2018 now, non-lexical lifetimes are a bigger recent improvement: https://doc.rust-lang.org/nightly/edition-guide/rust-2018/ow...

>> Chrome's appeal was primarily technical. Each tab got its own process and could crash without taking down the entire browser.

>Curious, I remember speed being the primary reason

It was probably both. I know I was definitely sick of sites (mostly Flash) crashing the browser and throwing my entire session in the bin. I was probably already using some Gecko-based "light" browser instead of Firefox, but V8 did make a difference when using the emerging web app style sites like Gmail.

I know I'm in a strange place when installing and updating some packages that were left out of the default installation of a particular flavour of your OS distribution is considered "crazy".

Nothing he described is in any way limited to servers. Even kernel live patching is available to Ubuntu desktop users for free: https://www.ubuntu.com/livepatch

The Rust examples seemed a little bit oddly structured to me; the case of collecting a value from a single thread would be just as easily solved by returning from the closure and receiving it through join(): https://gist.github.com/lorkki/e7386df8fff186b3e473994e9d31b...

The power of channels could be illustrated better by adapting the next example to show how you can avoid shared state completely: https://gist.github.com/lorkki/e7386df8fff186b3e473994e9d31b...

It's also worth noting that a more versatile channel implementation than mpsc can be found in the crossbeam crate, in case you're thinking of using them for anything more serious.

Speaking from personal experience as someone who often seems that way, it's because environmentalism is a rational argument that people can easily approach without having the urge to defend their own morality (which doesn't make for great dinner conversation).

Are you sure you don't mean that USB 1.2 was changed to USB 2.0? I don't recall any naming confusion between USB 2.0 (480 Mbit/s) and 3.x (5 Gbit/s and up).

>There wasn't much space for user tracking, analytics, etc.

You literally sent every keypress to a remote server that was responsible for both generating all of the views and storing all of the data you touched during that session. It may not have been called user tracking, but the sysops definitely had the capability to see everything that you did.

It sounds not unlike what used to be the role of W3C before HTML5. Everything stagnated, while Microsoft with IE largely did not care, and everyone ended up making their pages in Flash because it was the only really consistent target.

It should make no difference to an existing installation. The point releases to LTS really just mean that the installer images are kept up to date.

Slacking is what the current system conditions the long-term unemployed to do.

That is, the alternative to UBI here isn't "no income"; we already have basic income in Finland, though it's highly dependent on enduring various activation measures that are mostly useless in providing actual employment (and, in a few instances, have turned out to be sweat shops that use the unemployed for unpaid labour). Accepting a low-income, part-time job tends to result in the automatic loss of several months of basic income, though the pay from such job might be significantly less - so, in a situation where there aren't enough jobs to go around, the rational thing to do is to avoid any actual work and to simply keep jumping the hoops.

The proposed UBI models are aimed specifially at unraveling these "welfare traps" and at reducing the attached bureaucracy.

They're a nice feature, although after a long while of trying, I ended up using just the Facebook container. The main container extension felt like too much work in regular browsing, and the tracking protection seems otherwise adequate when combined with uBlock.

Sadly, Mozilla also seem to promote containers as an alternative to user profiles, while they're nowhere near as full-featured - sharing saved logins and bookmarks between my "personal" and "work" containers is almost never desireable. Managing and switching profiles, on the other hand, is virtually unchanged since the Netscape Communicator days.

The use and magnitude of font hinting is largely what makes the difference. Windows used aggressive hinting until Windows 8, and it's also the default in many Linux distributions.

For me, "blurry" ie. antialiased is much better, so long as it results in better defined letter forms, as it does on MacOS or when using freetype with hinting set to low or turned off. HiDPI simply means there's no tradeoff.

Myst was predated - and for some time, outsold - slightly by The 7th Guest, which was very similar in all those respects.

Neither of them were the first graphical adventure games without an inventory, as Loom had come out three years before. Several had likewise been in a first person view, perhaps most notably the MacVenture series in the 80s. The first CD-ROM game was The Manhole in 1989, which had the same designers as Myst.

Generally speaking, none of the individual pieces were particularly innovative, but Myst pulled them off well enough and in a simple enough package to appeal to people who didn't want to _learn_ to play a game. That's a merit unto itself.

Same concerns for me in HiDPI on the desktop. I suspect it's due to mixing em and pixel alignments.

> It does not leave room for anything that doesn't fit into some arbitrary set of database columns or set of graph nodes or ML model; no room for nuance; no allowance for change or for the unknown or for the unexpected.

Why not, though? Obviusly that sets limits on what kind of output the device itself can produce from each source of data, but that's not your entire experience of life as its user. To me it seems akin to saying that carrying a scrapbook would make you live in the past.

They don't really advertise it, but there's no requirement to use DRM on Steam: http://steam.wikia.com/wiki/List_of_DRM-free_games

> IPv6 only devices

That would be an interesting choice to make, seeing as the surrounding infrastructure is still transitioning and you can just as easily support both stacks. The real obstacles are legacy devices and misconfigured appliances, which can't simply switch over without anyone noticing.

Let's not forget, that's essentially how much of the IT industry as we know it got started: companies like Western Electric, AT&T and Xerox hired people specifically to innovate.

Though, in the finest academic tradition, once you try to actually run it, you'll find that it silently depends on a separate library written by the author, which you'll have to find yourself.

(In this case "tensorcv", which is in a separate repository: https://github.com/conan7882/DeepVision-tensorflow )

That aside, I agree that it's an easier read than most ML code.

> Recently (just as most of the world has apparently moved on from desktop computing, haha) Linux is pretty much fine for the traditional desktop computing.

It's been fine for the past decade, it's just the trope of "Linux on the desktop" that's slow to die.

I agree that there's a sound reason for this, but I can't help but think that API versioning would be the more correct way to do it. This is how you pile up unnecessary complexity.

That sounds a bit too juicy to be true. Any citations?

Yeah, it would make more sense to just add the new line printing shorthands and leave cin/cout/cerr alone. Overloading "for" as a loop over a range of integers also seems questionable, and it seems you'd need to pollute the scope outside of the loop each time you don't want to start from 0.

If someone wants to save the trouble and just run it: https://github.com/lorkki/xmosaic-1.0

It was interesting to see just how easy it can be to get software to build a whole 25 years later.