Well, rascist content tends to denigrate and harm people, it causes people to get killed and injured, while pro-LGBT content tends to call for love and allow people to love who they want.
I can see the difference, can you?
You make it sound like some slippery slope fallacy, but it's not the same speech. Calling for hate is wrong and should be shuttered in the darkness.
Any citations to your claim that most people care 'a ton'? I think most people would prefer simpler stuff over the flash if they could see the benefits but i have no proof, so i won't claim it's a fact.
The reader mode note was simply to say I prefer the text only style.
The second paragraph is there because this article is talking about a simple web page, and I'm complaining that more sites don't do simple styles.
I'm not sure why you had to be so condescending about my comment, maybe you're a designer?
Anyone anyone says 'aesthetic', I instantly feel like they don't care about usability or UX. I use reader mode most of the time on the web, for almost every page, and I've never thought that I wanted to see some flashy colors, fancy fonts, or moving/animated elements.
When I read an article, I want to get the content immediately, in a dark theme, with a readable font and size/spacing. Instead, i get 3 popups, 2 banners i can't close, a bright white background, some crap webfont, several MB of ads and social media garbage, etc.
The web has devolved from what it was without the 'flash'.
You're comparing a fixed medium, movies, with a dynamic medium, games. I'm not sure VR will be a long term success, but it will have no relation to 3D TVs failure.
Alpha is the worst internally (than gamma or beta) because it's a big particle (2 protons, 2 neutrons) and does lots of damage internally but can't pass through skin or clothes, so externally it's less dangerous. Additionally, the alpha particle can cause minerals in the body to become radioactive, thus extending the danger.
The original comment was about Turing completeness, and it was defined incorrectly. I was giving an example of a dead-simple language that was Turing complete, because the claim was that metaprogramming made C++ Turing complete.
It's Turing complete because it could simulate a Turing machine, not because of metaprogramming. The language brainfuck is Turing complete, for example.
Context free means something different to what you're saying here. This is a good discussion of this topic, I never knew C++ was so irregular and informal.
I made it a policy to only use a-z, 0-9, and _ in any branch, file, folder, or any other 'names' in the cli. Basically anything I'd type in the cli as an identifier/name. I find it prevents weird issues with characters when scripting and such, since the rest of the shiftable symbols on the 1-0 row (*, &, etc.) tend to cause issues when used too much in names because they're also used as operators and stuff. I think I started doing that with Windows filenames, since it has so many limits, and it crossed over into my Linux cli workflow.
There are a lot of really nice frameworks, like elixir with nerves, which make iot development a breeze. I'm sure it's not a pancea, but it's easier than coding in C or something like that for your firmware. With nerves, you can write your backend and firmware in the same language (elixir) and you don't need to worry too much about embedded things like memory insufficiency since nerves handles it all. I'm sure there are cases where you have to use a low level language, but those will decrease over time as hardware gets better and more efficient.
I would guess most folks here use full disk encryption, which would generally preclude you from reading the filesystem if you don't have the password any longer. If not, this is a good article to convince you to do so since anyone could do something similar to your laptop with no encryption.
I think there's someone who would accept working at each of those places just fine. Even the worst ones. Her point is probably more that if a company admitted their experience up front, people who thought that way was fine would accept jobs and those that hated the idea of that experience wouldn't. Sure, companies could lie, but then people would just quit as soon as possible if they really hated the experience. I'd work at any of those companies myself if the situation was right otherwise.
I'm sure because handshake is such a system and there are many ways to skin a cat, and it's not a problem that I'd classify as 'hard' in a technical sense, such as useful quantum computing or terraforming Mars which both may or may not be possible. The hard part here is getting people to use it, the network effects.
I do agree with what you wrote about the tradeoffs with the current solutions, but those are tractable problems, I believe.
I wish i had the option of turning off the ML autocorrect since it sucks but leave some basic features. Google is always all or nothing, it's fucking stupid. Like, i have to turn on my location history to give my wife my location in Google maps, no thanks, but it would be nice to share with her without that privacy busting crap.
There's other ways to do distributed DNS, I'm sure, than a cryptographic hash. I haven't looked into it much, but "Handshake" is a new distributed DNS system that supposedly works very well. I used to be averse to that idea, but this .org issue clearly shows we cannot trust icann much longer.
The 100k is over 4 years and tends to be mostly from "room and board" costs rather than the actual cost of credits. So the courses might be 10k a year and housing is 15k, for example.
Erlang/OTP and BEAM have been around a long time and is probably just as mature as the JVM and Java, but they have slightly different goals: very low tail latency, easy error recovery, and easy distributed compute in erlang vs. better customization and median performance for the JVM. I'm sure there's more differences and more nuance than that, but I'd be very happy to use either language/VM in production.
I think the "cloud" is helping to make it seamless to go from iPad to desktop to phone with one work item (like a report for work), but it's not quite there yet, I agree.
(I think in the Star Trek universe you would just reclaim the PADD in the replicator once you're fully done with it rather than move it around to some central "PADD library", right?)
RPC is basically built in, so you'll probably never use REST internally. There's an in memory database built in (ETS) that will replace redis for most key value storage cases. There's easy recovery from crashes via supervision trees and associated features. You can do hot upgrades while your system is fully operational.