1,270 karma · joined December 3, 2015
It sounds like the complaints here are operator overloading, global allocator by default, and metaprogramming. I think the value of these features are certainly not objective, but it's not a very compelling argument to avoid a language because of them.
As for optional standard library support, this is actually really common in Rust and is a breeze to support. Just annotating [no_std] basically gets you there libc wise. There's even additional restrictions like [no_core] to remove even more. I believe this should be noted.
I think the author missed an opportunity to really drill into actual pain points like the steep learning curves to c++ and rust, and where/if Zig excels in specific examples.
</rust evangelism strike force>
I believe this isn't an existential threat to the company by any means.
I switched to 1Password from KeePass after 5 or so years because I just got tired of maintaining the data locally and keeping it in sync on my devices that I need the passwords on. I just backup the 1Password database locally now to calm some paranoia.
[0]: https://gist.github.com/mooman219/9698a531c932c08ccefd86ba7c...
> The type of material for UV LED is AlGaN, which will have a layer of aluminum grown on top of GaN on either Sapphire or SiC substrate. Aluminum as metal is conductive, but on AlGaN it is not. To get to a far UV band like 222nm, high density of aluminum needs to grow, which becomes non-conductive. You would need to compensate it with extremely high voltage current to generate really low level of wattage, let alone all the heat it generates. So there is no commercial vitality to it. That's the reason the whole industry on 222nm is on excimer light.
This is a gist of some comments on: https://www.reddit.com/r/Optics/comments/fyqhht/how_are_leds...
I do a significant amount of text engine work and I'm skeptical what they implied by this. The likely case is they glued together other solutions (Like HarfBuzz/FreeType/etc) and expose their own API on top of that. This is perfectly acceptable and even encouraged for accessibility reasons. It may be that CoreText isn't acceptable for their use case.
What I think this would be misinterpreted as them writing the whole stack from scratch. For example, shaping is part of layout and it would be monumental if they wrote their own shaper given even HarfBuzz, DirectWrite, and CoreText do not have complete coverage yet. Additionally, BiDi + line breaking + shaping has bugs even in Chrome on some edge cases.
The point of my first comment is that the timing of this breakdown doesn't encapsulate the full picture, and getting a handle on their relative numbers would mean looking at a few cycles over a longer period. I agree that they have "nowhere else to go but up", but the comparison in the article listed is a bit shallow.
I tried to leave a review with what I said above, but it was flagged and removed. I got an email that it didn't meet review requirements.
This has been going on in Minecraft for more than 10 years. Large servers can pull millions of unique players a month and have >50,000 concurrent players. Some even employ competitively paid full time engineers. Even fairly generic servers that are well monetized and supported by a large youtuber can pull the range of 6 figures a year.
There's even a solid argument that the earlier predecessors to modern battle royale games were Minecraft Hunger Game servers in as early as 2011. We didn't even get DayZ until mid 2012. Between the ease of the bukkit API, ease to setup a server, and flexibility of the client, there was a lot of rapid prototyping of what essentially were software startups going on back in the earlier days. I'm not sure what the scene looks like today, but it was a blast back then.
It's really amazing to see games that can host mods in an accessible way doing well. I wonder how much better Minecraft could have been if they weren't actively hostile to developers.
I'm doubtful that any of these prices are representative of what the majority of the population has access to.