readittwice

Well, there are some stability issues with my ryzen 2700x. At first there were CPU freezes in idle on Linux: https://bugzilla.kernel.org/show_bug.cgi?id=196683.

After applying workarounds, I still see some strange crashes, not sure if at least some of those are still related to the CPU hangs from the bug above. TBF this might not be the CPU's fault. This is all quite annoying to me and time intensive to investigate (where do I even start?). Even though I really like AMD's tech I am quite frustrated and I haven't had these problems with my previous Intel builds so far...

aren't they already back?

> A linear memory is a contiguous, mutable array of raw bytes. Such a memory is created with an initial size but can be grown dynamically. A program can load and store values from/to a linear memory at any byte address (including unaligned). Integer loads and stores can specify a storage size which is smaller than the size of the respective value type. A trap occurs if an access is not within the bounds of the current memory size.

WASM has bounds checking on the linear memory as well.

> WebAssembly is still not safe from internal memory corruption, due to lack of memory tagging and bounds checking.

Unsafe applications won't ever be magically safe when compiling them to WebAssembly. Neither would this be the case when compiling to Java bytecode - if this was possible at all.

IMHO WebAssembly is a compilation target and therefore not the right layer to solve this. This is the responsibility of the language or the specific application. If you want to solve this in WASM, I predict you couldn't just compile all different languages to WASM anymore without significant changes to the codebases. If this would be feasible at all..

Rewriting those huge C/C++ codebases is simply not an option, new applications can be written in safe languages and then compiled to WASM.

> None of your examples demostrate how this party would be in the center.

I was merely arguing that party is center-right. I think I brought some examples, but obviously I am biased as well. Makes me curious how you categorize other parties in Europe if the Austrian conservatives are already right-wings to you (think Orban, FPO, Le Pen, Golden Dawn, NPD,...)

> I for instance worry a lot because the policies set in place in the last few months are dangerous.

This is where I really disagree, so many of these accusations are so blown out of proportion to me.

Best example to me was when some party leader of the opposition was literally speaking of "fascism", such that even the president (former leader of the green party) called that exaggerated. The opposition was arguing this way since before the government was even appointed, this is not just about the policies in the "last few months". Certainly a legitimate tactic of the opposition, but nothing I fear at all.

True, that's why I wrote "Dart had".

Well, the conservatives and the right are not going to implement left politics. Austria was certainly NOT converted into a "dystopian place".

Like it or not: Some time ago, a left-leaning newspaper (Standard) wrote that the current government has the best polls recorded so far.

Almost all your points are about immigration. Yes, they have certainly moved to the right on immigration. Even the centre-left social democrates have moved right in this regard. But that still doesn't make the conservatives a right-wing party.

Compared to the past they have also moved left on other topics: e.g. by not touching pensions.

"restricts skilled immigration": Funny, since they have also been criticized for allowing more immigration. Ironically from left-leaning people.

"reduce social support systems": Well, they mostly retargeted social support. All polls showed that a large majority of the people supported these changes. People thought the old system enforced the wrong incentives.

Also let's not forget that they reduced taxes on salaries specifically for working-class families substantially.

"lowers corporate tax rates": IIRC they have only lowered one tax slightly for a single sector (tourism) so far. Hardly anything dramatic.

Still, all these points are not too surprising for conservatives in general. If this is enough for you to call them right-wing, that's certainly fine for me.

Just to add: I've talked to people that directly called the Austrian conservatives an extreme right party ;) I know you didn't go as far, but they were also pretty serious about that. Maybe we can agree that at least "extrem right" is ridiculous. I personally don't get where this overly-dramatic phrasing comes from. Are some people so upset that for once the chancellor is not a social-democrat?

No, that's just your opinion. The OVP is center-right, the FPO is right wing/populistic.

Well I am skeptical about performance improvements due to type annotations as well. Other languages have similar different systems and didn't get faster.

Dart had gradual types but didn't enforce them at runtime because of performance. The PyPy devs don't believe that type annotations help them for performance (http://doc.pypy.org/en/latest/faq.html#would-type-annotation...). Also there is no JS engine that uses TypeScript annotations so far to improve performance.

Types are usually on the wrong boundary: e.g. Integer doesn't state whether that value fits into a register or is a Bignum.

Also: Aren't some type checks quite expensive? So more expensive than a simple map/class/shape check? E.g. passing an array from untyped code to a signature with something like `Array<Integer>`. Wouldn't a runtime that verifies signatures have to check all elements in the array to be actual Integers?

Isn't it a win because the goroutine now starts with 4K of stack instead of 2K? This makes the stack large enough, such that the stack doesn't have to expanded on every request.

It might make allocation a bit faster, but is this really where performance was lost?

I guess for the runtime it is more expensive to copy the stack contents (so nearly 2K) and e.g. update pointers in it (a simple memcpy might not be enough).

Well, in Austria there are a lot of people going to the dentist to Hungary as well because it's cheaper. The situation is a bit more subtle than you pretend it is.

Health insurance typically only covers the minimum at the dentist, and almost nothing of what is considered "cosmetic" or would be good in the long-run (e.g. oral hygiene, braces). It gets expensive quite fast.

Not sure why you think this is the case: there are numerous JITs/VMs that optimize starting from bytecode e.g. all JVMs, WebAssembly, V8, JSC,...

Can you point me to some paper/reference about this? AFAIK it doesn't matter whether you have an AST or bytecode. Optimizations are done on an IR anyways.

True, however I would argue that having an IR in general makes the code easier to understand and maintain. Especially if you add more optimizations.

Ember? It's supposed to be a Rails-like JS framework.

What do you mean with that? Honest question, I am not from the US.

They bought YouTube for a billion dollar - which was back then a crazy number. I still remember all that people arguing (including me) that Google would never make so much money back from YouTube. YouTube even had the reputation for being a huge loss for Google for multiple years.

I mean it's kinda true. But they still had to figure out that these were the projects/companies worth buying and afterwards pursuing and advancing them such that they would become the cash-cows they are today.

IMHO the Google Home devices and Chromecast are quite successful.

I admit these are probably not powerhouses on the level of Android, Chrome or YouTube. However it's just not possible to create a powerhouse every 1 or 2 years.

Google just recently abandoned Android and pushed ChromeOS for tablets. Now this, there is just no continuity with Google.

Unless you absolutely need Android for some reason, I would recommend the iPad.

Please correct me if am wrong: But I think both Chrome and Safari have disabled/removed their Spectre-mitigations in the JS engine.

Because she is famous (over 100K followers on twitter) ;)

On a more serious note: Because there are some books in this list that at least I've never heard about but sound interesting.

I looked into Pony some time ago and I always found the capabilities-thing to be quite complex although very interesting. It was hard to imagine using it in a project with developers unfamiliar to this concept. Especially since I was mostly working on large web applications where only tiny parts were actually using shared state between threads.

TBF I have never written Pony code, I was mostly reading documentation.

> What's great about the actor model is that you can kinda apply it in languages not having such native support.

Yep, although not listed in the article, JS would be such an example for me. TBH I am not entirely sure what's the difference between Web Workers and Isolates but for me it's more or less the same: Both allow safe multi-threading simply because threads do have separate heaps.

I personally would like to see an ARM competitor to the Intel NUC. 4GB and 4 cores sounds great but might not be enough for development or certain benchmarks. Something like 16GB RAM and at least 8 fast cores with a fast SSD should be enough. It seems that you can only get ~50$ devices or >2000$ servers (if they even sell single ones). I guess we have to wait for Apple to sell a MacBook with their own cpu.

I guess the situation is similar to containers and static linking that got popular for server deployments quite recently. They allow to develop, test and deploy your application with its dependencies in the exact same version - the exact same binary. Although usually this works just fine even with minor differences in the dependencies, a lot of developers deem it worthwhile to preclude such issues. If you now use ARM in production, you can't use the same binary file anymore.

There might be different implementations depending on the architecture in some library you use. Also even with higher-level languages like Java it is possible to observe ISA differences: e.g. memory ordering.

> Developers are using cheap Raspberry PIs as local desktop development platforms.

IMHO this is still a problem, it is easy to get RPi-style devices but for development a more powerful device would be great, however this is much harder to get. Sure, cross-compilation works but is usually tedious to setup and work with.

I've had the chance to work on one of these powerful ARM servers for some time. I was connected via ssh and mostly working with tmux+vim, I could compile natively with all these available cores and memory - development was a breeze.

Nevertheless there were some pain points compared to x86: Often no ARM64 binary packages, except for the packages provided by the distro. No precompiled binaries. Software wasn't working/building e.g. because Fedora on ARM64 uses 64K page size. perf didn't support as many performance counters as on x86. Sometimes I would've really liked to use rr (the reverse debugger) but it only supports x86. Pretty sure I've encountered more pain points that I don't remember and also I think I didn't discover all of them.

Development is almost exclusively done on x86. So it is only natural that x86 is the most tested and optimized architecture. This wouldn't be a problem if your offering would be much better/cheaper in some way and although I think ARM servers can compete in certain areas it doesn't seem to provide enough benefit to be worth the trouble. I agree with Linus that they should be focusing on developers and software and let the machines bubble up into the server segment.

Not sure that's what he was saying. I understood that instead of targeting the server-market directly first, he recommends that it would be better to target the developer market first. And if it's popular there, it will naturally bubble up from there into the server market.

Sure it will take more than a few tenth of a percent of mac developers but it won't need total domination like x86 either. But just imagine if Apple really just switches its MacBook (not even the Air or Pro ones) to ARM64 that would already be millions of users. A lot of devs will at least try to compile their app for that platform for the first time. Quite some developers will be curious and get one just to test their software on it. I am pretty sure this is going to help the adoption of ARM64 way more than a slightly improved CPU or another experimental support by a cloud provider.

Personally I don't care too much about ARM64's success (although more competition would certainly be great), I am more rooting for RISC-V and I hope they follow a more developer-first strategy.

Hinkel shouldn't have used this term, simply because Pinker was NOT mansplaining. And AFAIK Pinker isn't a billionaire either.

Calling them mansplaining billionairs is IMHO a cheap shot. Pinker and Hinkel have different opinions - which is perfectly fine, experts disagree a lot after all. But accusing someone of mansplaining just because of having a different opinion is not correct. An expert in this area should argue differently.