From https://github.com/fusionlanguage/fut/discussions/119#discus...

> I've read about Haxe in 2000s, before I started my work on Fusion. They have different design goals: in Haxe you create whole apps, in Fusion you create components to be used from other languages. Haxe has syntax similar to the (now dead) ActionScript, Fusion is similar to C#. Fusion transpiles to C, D, Swift, TypeScript, OpenCL and Haxe does not.

But what is the goal of Fusion then in pragmatic words? E.g. Haxe helps to save on development costs when targeting multiple platforms with emphasis on graphical interactive apps (games mostly).

Correct URL: https://ec.europa.eu/commission/presscorner/detail/en/ip_26_...

Seems the last bit of the url was cut off after submission.

Thank you

TypeScript: Every minor version has breaking changes and the next version after `n.9` is `(n+1).0`

They never go higher than .9? Why?!

Apparently for markting reasons.

https://github.com/Microsoft/TypeScript/issues/14116#issueco...

Wow. Also pretty funny that he says "if we followed semver rules exactly, literally every single release would be a major version bump".

Seems like quite a blase approach to the development of such a large project.

I always ask teams that say that: "OK, so every release will be major, what's the problem?"

I don't think anyone is losing sleep that we're on Chrome 86.0.4240.75 and that communicates exactly the amount of information I need to know if that's older or newer than another version.

I agree it's not semantic versioning, per se, and maybe not nice to developers but it's at least communicating clearly IMO.

I'm on version 83.0.4103.116 which is 3 major versions behind. I am averse to upgrading because it's working for me and I'm concerned about 3 rounds of incompatible/breaking changes. I have no idea about the relative maturity of the two versions, how big the breaking changes are or if they're likely to affect me, or how much time has transpired between the two versions. With every "major release" of Chromium my wariness increases, until the only way you'll get me to upgrade is when I'm forced to upgrade my system.

How is this communicating clearly or being helpful to me? Does anyone know offhand what major version of Chromium/Firefox they're using? If it's just an incremental counter, then why do we need .0.4103.116?

4240 - 4103 = 137 days between versions.

Javas implementation of HashMap uses a tree on hash collision.

[0] https://hg.openjdk.java.net/jdk8/jdk8/jdk/file/687fd7c7986d/...

If the bin is big enough to warrant it, according to your link.

Thanks for the link!

I imagine they do this as the user space can define hash algorithms and someone is gonna just return zero every now and then out of laziness :-)

You also need a comparable() key presumably - which you often have, but not always (a comparable() key is not strictly required by a hashtable).

See also https://news.ycombinator.com/item?id=21700117

One of the points has since been removed from reality: jemalloc was removed and the default allocator switched to system in 1.32 (January 2019)[0].

[0] https://github.com/rust-lang/rust/blob/master/RELEASES.md#co...

How do you redirect to the phishing site, if you are currently browsing an SSL encrypted website without making it to obvious? Since you get an error message in the browser...

That is correct. However it's trivial for a MiTM attacker to perform an SSL stripping attacks when the victim is communicating with sites that support plain HTTP.

even with HSTS?

If a website employs the use of HSTS all traffic will be redirected to HTTPS, rendering the support for HTTP redundant.

Hmm, if you can control the plaintext network isn't there an NTP attack to reverse time and use old compromisable certificates or move it forward past hsts max age?

take a look at the source:

https://github.com/SalmaanP/news_backend/blob/master/altsumm...