andoriyu

Qualcomm hasn't made a single Qualcomm core since Apple released their first aarch64 SoC. Qualcomm had zero competition and decided to not really work on anything. Apple blindsided it with its very competitive aarch64 cores, Qualcomm had nothing to show, so they switched to ARM's core design.

Customers kept paying Qualcomm for their SoC with ARM designed cores, so once again, Qualcomm had no reason to actually do anything but sit on their patents.

Intel had a similar story, since Sandy Bridge "x86_64" part of CPU barely changed, most of the performance gain was somewhere from better process, more custom instructions (avx2, etc.), higher TDP (since ryzen).

It's not ARM vs x86, it's Apple ARM cores vs everyone elses cores.

That's exactly the case. Any YAML 1.2 parser can parse any valid json document as is.

> I dunno here, is Rails a server application library because I can progressively integrate the different components of its total API, e.g. first use ActiveRecord, then adopt rails-api for the frontend, then adopt ActiveView and Turbolinks for the end-user frontend? Or is there different idea of framework at work here?

I think you misunderstood parent comment. Progressively integrate here means: you have a web page (facebook.com), you want to replace a part of it with react (chat function), you rewrite just that portion of the webpage in react.

You can't get a Sinatra application and replace just one route with rails. Well, you can use ActiveController, which is just an opinionated wrapper around Rack with a lot of sugar, but that wouldn't be rails and you won't get any rails benefits of doing that.

That was satirical, lmao.

Agreed. I think bash is a dependency. Even more, it's a dependency I'd want to avoid at all cost.

Let's see. They don't approve for other platform because "they want dartvm to be cross-platform and not hold too much platform dependent code"

Then they proceed adding platform dependent code for their vanity projects like Fuchsia along side their other platform dependent code for not vanity projects like ChromeOS and Android.

IMO Dart is only alive because of Flutter, outside of it, it's dead.

That's not the case for a long time. I have rEFInd that started life in windows 7 esp with freebsd dual booting, now the same hard-drive booting windows 10 (upgraded from 7, not fresh installation) and nixos, all with the same rEFInd from the same.

The correct way to do so, is to have separate hard-drives for different OS. Then there is zero chance of them stepping on each other.

Firefox, gecko specifically, performed very bad on Mac OS X when chrome just came out.

That was also an era of websites crashing all the damn time - in firefox it was crashing the entire browser.

Chrome was a significantly better browser for a while. Now it's just "why switch?" to your average consumer.

> Process per connection is pretty easy to accidentally run into, even at small scale. So now you need to manage another piece of infrastructure to deal with it.

Most places I saw this as an issue, are where developers think that by tweaking the number of connections will give them a linear boost in performance. Those are the same people that think adding more writers in RWLock will improve writing performance.

I agree that it's easy to run into and pretty silly concurrency pattern for today's time. At the same time, it's just a thing you need to be aware of when using PostgreSQL and design your service with that in mind.

IPv6 privacy issue? You know that you get /32 block, you can change your IP from that block every hour if you want.

The issue with IPv6 is that links are significantly slower than IPv4 links today.

see: https://tools.ietf.org/html/rfc4941

I don't get how 1d array is slower than 1d vec. Both doing the same arithmetic, but vec has to do one extra operation.

That's a requirment for any language that isn't allocating everything on heap. Nothing to do with borrow checker.

OutOfBounds errors aren't checked at compile time unless it's a `const` type IIRC.

But it's not a file type, it's a file extension that sometimes can be matched to a content type.

But C++ does have opt-in memory safety via smart pointers and RAII. It's not preventing all the bug types hat rust will, but it is. There is also tons of code written without it, but you get the idea.

Zig misses a lot of futures that modern C++ has without offering anything in return. Yeah, it's easy to learn compared to C++ and Rust, but what the point of learning it if doesn't offer anything new?

How is adding `Duration` to `DateTime` related to jupyter notebook? I use that much more often than element-wise matrix multiplication.

You know, I agree that shipping the same damm Unicode table over and over is stupid.

However, if they were part of the OS sooner rather than later, certain OS vendors would have found a way to make them incompatible or distribute them separately and make the user explicitly install them. (if you play in Windows, how many times and how many versions of VC++ redistributable you had to install?)

I remember there were projects where I opted-in into writing my own parser (with Pest or nom) just to avoid depending on regex crate. Which is usually the biggest dependency in my projects.

Please read beyond title. Product in place is not Docker, but Docker for Mac. A product that can't be replaced by podman.

Not really, it was pretty verbose, but wasn't hard. Pinning is for setting package priority between multiple repos.

What you're looking apt is apt-holding:

apt-mark hold libxfont1

That been around since 2013 IIRC. And there was dpkg way of doing it before.

Correctly if I'm wrong, but IIRC low-level futures are very dependent on executor? I think you actually told me that, but that was back in futures 0.1 era.

It's complicated. Thunderbolt 1/2/3 were all open-ish, but required intel's chip. Which was alright at the time - AMD didn't have anything competitive in mid to high-end market anyway. Thunderbolt 3 later became royalty-free, but with mandatory certification by intel.

Around January 2020 vendors are able to make their own controllers and submit them for certification. AMD doesn't have any. Intel's controllers don't have an embedded version for sale.

Scale, USPS deliver far more mail than others. USPS had pretty specific requirements and not a single existing truck existed or could pass an endurance test.

Good video on subject: https://www.youtube.com/watch?v=RE5FGyq12ds

Not really, CPU is still "of-the-shelf". SoC is custom. That's just because you can't buy Neoverse and drop it into the motherboard, so making a custom SoC is the only way to obtain it.

Donut has a good video about LLV: https://www.youtube.com/watch?v=RE5FGyq12ds

While most is true, rfc3339 isn't a profile of iso8601. Both have cases when it's not valid in another.

Sure, `20201209T160953Z` or 2021-123.

yeah, until you meet the system with different make, and now you have to install GNU/Make.

The difference is - your script works out of the box, or you need to install ripgrep.

Well, Rust (or any language) won't prevent business logic bugs.

> Or does the author mean "works" in that it runs where an interpreted language would not (i.e, syntax error)?

More than that, but close. i.e. you won't get NPE from java. Syntax error or type mismatch from interpreted language.

In addition, NewType pattern will stop you from passing seconds into a function that takes ms and vice versa. You won't get data races. You also won't get an `undefined is not an object`.

Long story short, due to language verbosity it's hard to make logical mistakes.

uhm no.

Rust's "unsafe" is a pretty bad name and completely different reasoning behind using it. It doesn't mark something as "dangerously unsafe, don't use", to a consumer it indicates "exercise caution" and to a compiler it just allows 5 things:

    Dereference a raw pointer
    Call an unsafe function or method
    Access or modify a mutable static variable
    Implement an unsafe trait
    Access fields of unions

The point of "unsafe" in rust is to highlight which area requires more human attention... not to discourage its usage.

`dangerouslySetInnerHTML` is literally dangerous and allows XSS if used with outside input.

It also is faster than the other variant. The same is true for `random()`. Both can be used when you know what are you doing to gain some performance.

Meanwhile, `unsafe` rust by itself is not different from safe rust in terms of speed. You have no choice, but to use it places it supposed to be used.

> Also, does Zoom work on FreeBSD?

I used Zoom on FreeBSD. By use I mean I was able to be in a meeting, see screen share, share my screen, but I had to dial in for audio and never tried webcam.

If we're talking about long term investment than dollar cost averaging is about the same as lump sum on January 1st.

As for starting an ETF... Well minimal capital requirement is 100k, to launch it's probably 300k total investment. Then there is a lot of legal requirements and obligations. Whole process is at least 6 months

I guess it depends on what's your goal. Some brokerages let you create a bundle of stocks and share them publicly or privately. Which is sound more like what you want.