This is not a solution. The average rent is still $1832, which is still unaffordable for people in Denver making the median income of $54.3k if you apply the rule of thumb where rent shouldn't exceed 30% of your monthly income.
Ah yes, woke, the word used to describe something disliked.
That's a misrepresentation of what's actually going on in the R4L project. Volunteers are enabling support for it within the kernel to allow for rust drivers in a way that explicitly does not require existing maintainers to change how they maintain their parts of the kernel. Maintaining rust support and the APIs consumed by Rust is the job of R4L and doesn't require any work from the existing maintainers who are allowed to make changes to their C that breaks Rust where the Rust will then be adjusted accordingly.
Unfortunately yes, they'll send you a C&D if you pop up on an Oracle lawyer's radar. A coworker of mine had a course named "Rust for JavaScript developers" and received a C&D from Oracle.
1. I can pin my json parser dependency and literally never update it again
2. And how many times have we seen 20 lines of C backfire with some sort of memory safety issue.
3. First off, i'd go out on a limb and say the number of attacks from a well-established (or even a naive one) rust json parsing library is dwarfed by the number of attacks from adhoc config parsers written in C with some overlooked memory safety issue.
4. Usually being the key word, tons of adhoc config formats have weird shit in them. With json (or yaml/toml) you know what you're getting into and you immediately know what you're able and unable to do.
It works great for 90% of use cases, but getting that last 10% to work is really really hard so Bun (and node 22 which supports the same thing with an experimental) just throws an error in those cases. The most notable thing is `require`-ing an async ESM module from CJS, because require is a synchronous call you cant just async-ify it trivially.
Mostly curious, why do you care about the readability of the generated JS? Surely if you need to debug something for a production bundle you can use source maps.
One thing I'm not sure about when reading their policy is what'll happen in another kik situation. If someone were to claim the scope Microsoft (for example) that had no relation to Microsoft and then Microsoft came along and wanted the scope what would happen?
If MS got the scope what would happen to the packages in that scope, or if MS didn't get it what is done to clearly communicate that this is an unofficial account (presumably) asking on MS' behalf? In this early on period I'd expect a lot of people to claim the scopes of notable companies and these companies might take issue with that if they choose to use jsr down the line.
Even with their constraints they could have made this nicer, especially around the default formatter. Always requiring an explicit formatter is a classic example of Java being unnecessarily verbose, `\{ ` already wasn't permitted by previous java compilers as it was an unknown escape sequence so we could have nicer templates for the stock formatting like "\{foo} bar".
People have reasons, personally I don't like placing the burden of a viral license on people. I don't write code to further a copy-left cause, I write it to build things and make it easier for other people to build things.
What card could you have bought that lost support months later? I can't think of any new card you could have bought that'd lose support that quickly as far back as 2016
The vast majority of those sales are for GTA online, which this leak doesn't inherently give you access to. I don't see this leak financially harming Rockstar more than the cost of the presumed ransom, people still have to pay to play GTA online.
I highly recommend anyone using this to use a Durable Object https://developers.cloudflare.com/durable-objects/ for writes as this project doesn't seem to have consistency guarantees. If the Worker that writes to a collection happens to both do a write at the same time the data will be whatever the last Worker to write set it to.
Very cool library for read-centric use cases but I'd be very careful using this for use cases with frequent writes.
> we can already see this by compiling build and proc macro crates with optimizations, it's just not the default and they still have to be compiled once.
I'm hopeful something like watt (https://github.com/dtolnay/watt) will land in Cargo that'll allow us to ship pre-compiled wasm blobs for proc-macros so we can just have sandboxed binaries.
The free tier gets 100k requests per day, not month. And then for $5 you get 10M or 1M free a month depending on your settings and then you get charged for additional usage.
I don't really consume HDR content through Youtube,so the Chromium relation doesn't have much bearing on my situation. Although it does make me sad that the only browser that really caters to what I want from a technical perspective is Chromium, I'd love to continue daily driving Firefox.
Some youtube videos have it now, but not really. I ripped all my blurays and have them hosted on Jellyfin for consumption which I prefer to use as just a tab in my browser than their dedicated player.
If a repair shops wipes someone's phone they'll be pissed, but they aren't going to throw out the phone. As soon as they get back that phone they'll reinstall all their apps and log back into all their accounts and any malicious firmware added by that repair shop will wreak havoc.
I 100% agree that we should have ways of getting rid of these warnings on our own devices, but this isn't a simple problem.
With how powerful the type system is you can implement pattern matching via a library pretty convincingly, https://github.com/gvergnaud/ts-pattern is definitely the go-to. That being said pattern matching is hardly a requirement for being ok for implementing compilers.
Ease of use is the biggest one. While you and I are capable of setting up and keeping up a remote machine with a self-hosted password manager, I'm incredibly confident my barely tech literate parents are. Realistically for people that aren't savvy enough to set up their own thing it's a e2ee password manager using that password manager's remote service or them using the same password for multiple websites and more of a lesser of two evils.
Incredibly reasonable. People love to trash on the performance of Python and JS saying that they're totally unsuitable for backend services with non-trivial amounts of traffic when they're usually the most cost effective solution for a business. These higher level languages are easier to hire for, much easier to prototype, allow for faster iteration, allow for substantially faster on-ramp time, and are fast enough to run these io bound workloads.
I'm really sad that the list of trustworthy registrars is so small. I use Cloudflare for most of my domains and then Google for my .dev domains but now I'm not sure what I'm going to do with my .dev domains, probably keep them on square space. I'd love for CF to get more TLDs on their registrar because I'm very confident that registration isn't something they'd ever kill but there's a told of niche TLDs they don't have yet.
> not an average or a number any significant fraction of users would be hitting any significant fraction of the time
Mhm and no major third party reddit app is going anywhere near that with their 500 requests per day per user.
> An app aggregating many users, if reasonably efficient, would be expected to have an average per-user rate over time much much lower than the single-user, single-moment absolute limit.
The per user rate of these apps is 500 a day, which is reasonably efficient. Your point of them being "grossly inefficient" is just false.
These apps aren't grossly inefficient though, they've been substantially lower than the 84k per user per day API limit that reddit has held in the past for these applications, typically being below 500 requests per user per day. Even reddit's official app uses more API requests per day.
Probably portability, it's a pretty good low (but not too low) abstraction layer over the systems preferred graphics API. I'm not a graphics programmer but my understanding is it's closer to vulkan or metal in terms of control over the hardware compared to OpenGL, which has rocky support on Mac now anyways.
With frontend a lot of what engineers are tasked to make (highly interactive websites that still have decent SEO and time to FMP), you need to add some complexity to achieve that. SSR + hydration for web apps has been common for years because it's great for SEO and getting a fast paint and because of that we now have these super established hybrid (as in client side and server side rendered) frameworks. Sure you can implement these sites with an html file and some JS to populate it with data, but it's hardly a nice and *easily maintainable* experience when dealing with non-trivial applications.
And now that your app is using one of these frameworks, you probably need some sort of API for whatever. There's a lot to be said about designing a REST api just being exporting an JS function in a file in a /api folder or whatever. If you are already using a hosted option for these frameworks it's an incredibly simple solution that doesn't require to you mess around creating a new project, making a docker image, going to a different cloud provider and giving them your credit card, etc. And depending on your scale that might genuinely be cheaper than running a container 24/7 on a public cloud.
This is not the case, websites behind will get good ddos mitigation to begin with some options for improving that for some cost. But it's worth noting that in 2022 they blocked a 26M req/s attack on a website using the free plan, imo that's very generous for someone not paying for ddos protection.