I thought both Thread and Zigbee run on top of IEEE802.15.4, but Thread is based on 6LoWPAN / IPv6 where Zigbee uses its own network layer. But Thread idd functions fine without the internet (although you probably could connect devices to the internet if you'd want to).
... which is why we want to use FFI instead ;-) Now you already can using JNA though. JNI still requires you to write native code and compile it for your target platform, FFI eliminates that need.
I used to do Hello Fresh regularly too, but I quit using it after about a year. Thing is, it's about 7 euros per meal per person, and when you're comfortable enough to cook the meals yourself, just getting the ingredients from the grocery store takes the cost to about 3 euros per person. Which saves about 20 euros per week. As someone said above, teach a man how to fish. The recipes are quite useful in that regard though. That being said, it takes a bit of extra time to compile your shopping list, so I guess you need to factor that in too. But since you need to go to the grocery store anyway, I think it's negligible.
IMHO that does not matter. If they knew about the software, they are the ones responsible, not the engineers. And it seems unthinkable that engineering just went ahead and put in the software hack, without getting a go from management or the compliance dept. It's about who signed this off.
I don't think he refers to the caching being a bad thing, but that it probably does not affect performance that much, since most Strings are likely to be small (and the number of times hashcode is called is also likely to be small).
There's also a catch : if the hashcode of the string is 0, the hashcode will be recalculated every time (since the code assumes it has not been cached yet).
Shouldn't they also take other factors into account, like image quality, sound quality, connectivity and the likes? Seems rather easy just to slap a "quality" label onto a TV just based on how well it runs the Netflix client.
Why do you say Soekris dropped the ball? I've been running Gentoo on a net5501 for years now (since 2009) and never had any problems except with the USB (which I'm using to read out my SMA inverter).
In the case of EJB and so on, it's not just OO concepts. You also have declarative distributed transactions and nesting of these transactions, role based security with a shared context. I thought the concepts were originally based on CORBA, which is even older.
Technically it's EJB (Enterprise Java Beans), JavaBeans is a pattern where you need to adhere to particular coding conventions (getters, setters, naming of said getters and setters).
I also used to work with these a long time ago (EJB 1.1 and 2.0). A lot has changed since then though, and EJB 3 has solved a lot of the pain points (arguably pushed by the success of concepts used in Spring and Hibernate, whose authors served in the JCP for the newer JEE specs).
I get what you are saying, but you do make it sound like the (older) people with children are the worst ones, by virtue of having children or being older. Also there is a reason why these measures are in place, being that people with children have more risk (more expenses and responsibility) and are less mobile. And older people typically have a harder time in the job market.
Yeah but it's not the UI that's laggy. It's mostly the library updates. I've got a Raspberry that takes 15 minutes to do a library scan, while my Ion takes about a minute, maybe 2. It depends on your use case of course, but when you use sickbeard, you end up doing library updates almost daily.