Were it not for the pandemic, you might have a point. But there are real risks associated with being physically around other people right now, particularly if the offices happen to be poorly ventilated open offices. Amazon's offices spaces are notoriously (in the Seattle area, where I lived and worked until recently) not exactly fantastic in that regard. I can see the reluctance to RTO based on that alone.
... only 8GB ram is intentionally shitting all over your customers.
haha, man. the first pc video card i ever owned had two megabytes of vram and that felt *huge*. how times change!
"Sorry I can't come to work today, boss. I've developed a bad case of rectal glaucoma: I just can't see my ass coming in!"
Film at 11.
This is why that meeting that could've been an email
openbsd rules.
to make something approaching real content here though, I gave openbsd 7.0 a spin recently for something and the upgrade to 7.1 was incredibly polished compared to the last time I used openbsd (circa 3.0), on par with something like an Ubuntu dist-upgrade, and package management vastly improved. big thumbs up to the team for the usability work that went in on those areas!
transmet is a delightfully bonkers sci-fi/political thriller epic; the series has completed and is available as a (ten? iirc?) volume collection via amazon et al.
If it was just a matter of the business owners saying "no, go away" that'd be one thing. When they organized mass harassment against the plaintiffs, that's a different matter altogether, and that part seems to be missing from much of the media coverage of the case (particularly on right-biased media sources).
Bruce Schneier did not boycott the RSA Conference. Instead, Schneier also attended TrustyCon.
The default configs for postgres are set for a fairly small memory usage profile (*), which is fine if that's what you need (e.g. tiny vm or something that makes it a huge production to raise things like max shm size), but if you have sufficient ram, you can crank a hell of a lot more performance out of the engine by making the configs less conservative. This page is a good start: http://wiki.postgresql.org/wiki/Tuning_Your_PostgreSQL_Server
Not that it's a priori *wrong* to run with the defaults, it'll still work just fine, but once you start having significant traffic or complicated queries you'll be happier if it more fully uses the system resources available.
(*) It's been a good while since I last had to take a pg instance from stock and tune it, but I very vaguely recall the default settings were on the order of a eight megabytes of ram usage.
(assuming it really is a great school, which I have serious doubts)
For what it's worth, Cornell is currently ranked something like fifth in the US(*) in terms of their computer science department, and the Technion is hardly a degree mill either. I don't know what their hybrid programs are going to be like, but at least the source departments seem solid. Admittedly, rankings are largely bullshit and the student guarantees far more of outcome than the institution, but I don't think it's a stretch to say that the "Stanford/MIT/CMU/UCB/Cornell" group is good-to-great.
Not registering spurious taps is an even more key ingredient to an acceptable touchpad -- so those physical buttons had better be there after I disable tapping altogether.
There's a big difference between information about the programming interface of a device, and "blue prints" that would allow a competitor to easily implement a copy. It might make it easier to produce hardware that works with the same drivers, but probably not easier than just writing new drivers for totally unrelated hardware (unlike in the DOS days where drivers were embedded in application code, and hardware compatibility was the only reliable approach).
There is lots of hardware with open source drivers -- how often does that result in the hardware being cloned?
Of course, some devices are relatively simple things with all the intelligence in the driver software. In that case, you'd have more of a point (though you could still document the interface to the hardware itself), but that's more about selling software than preventing a clone of the simple hardware. It doesn't justify a general statement that Linux driver development is "pure hell".
Real Programmers don't write in FORTRAN. FORTRAN is for pipe stress freaks and crystallography weenies. FORTRAN is for wimp engineers who wear white socks.
