TheRealPomax

Which doesn't even make sense. You don't need JS to trigger a form with a GET method, nor do you need JS to render the serve response to that GET.

With all due respect: why does this need an LLM, and this much data? Surely a "classic" knowledge base with a more traditional search bar, running on top of the same data this LLM was trained on would be way smaller, and actually as trustworthy as the source material it surfaces for you?

The LLM weights are not tuned for truth, including citing sources, it's tuned for "doing as much as possible, as fast as possible, on your own". If you ask it for a source, it literally has to autocomplete one, it's not going to figure out which source is the most appropriate or authoritative as part of that text generation pass.

That's because they do, as well as in every other giant product, because security auditing has gotten quite a bit better.

You mean Saudi Arabia is shutting down Bioware?

Because you forgot to look at how many westerners move to other countries, too, and how many people in those countries move to western countries. You're asking a question based on an assumption that doesn't hold.

This could have done without the "I am a kitchen equipment nerd, you can stop rolling your eyes" immediately followed by "I thought induction tops used tempered glass but they don't??" intro undermining the rest of the article.

It's like a bit like someone opening their article with "I am a bit of a PC building nerd, stop rolling your eyes, so anyway I thought you could just plug an enterprise NVMe drive into any motherboard but it turns out you can't??"

Oh no question, biscoff is yours, I will give you that any day of the week (and then ask if I could have one, of course). Even speculoos is pretty much Belgian. But speculaas... come on author, you clearly did _some_ research, why get this wrong?

> traditional Belgian cookie speculaas

Pardon? You mean the traditional Belgian, Dutch, French, and German cookie? Because it's a cross-border (food) cultural good, it's not something invented by, or to this day cherished in, one specific country.

It would be nice to already see parts of the entire map coloured so you can see (extremely approximately) what's available.

Anything that's tied to hardware is one accident away from locking you out forever unless you set of "2 of 3" or some other "let's make life even worse when it comes to authentication" solution.

Someone never learned the "you don't fund this year's conference using this year's signups and sponsorships, you fund NEXT year's conference using this year's signups and sponsorships" rule that applies once your conference is an established yearly event. How the hell was there no contingency fund?

If I am an expert at using a hammer, no matter which hammer I buy, I know what the result of swinging it will be. If I am an expert at using an LLM, I have no idea what the actual result is going to be, and that's before considering a model update. Unlike being an expert at a tool like photoshop, where even 10 years of updates still lets me go "I know what is going to happen if I crop this image".

LLMs are not a tool, they are something else.

It does though, even if it shouldn't be blindly taken as gospel. Arguments help, but some folks have a better brand of apple box to stand on, and "I live and breathe git" helps quite a bit ;)

Yep. So was 1.46 x 10^48

For now. Turns out the pigeon hole principle still holds.

Perhaps not clear enough, but Scott was a cofounder of GitHub, so he knows a thing or two about git in the real world =)

Note that the US constitutional first amendment "freedom of speech and expression" and the Canadian charter's "freedom of expression" are not the same thing.

The Canadian charter explicitly allows for limits based on the (necessarily) vague concept of what a normal democratic society would consider fine, and what they would consider "how about you sit down, and reflect on what you just said because what the hell is wrong with you". And of course, context matters.

Calling a city worker something unpleasant because they refuse to issue a marriage license because of their personal beliefs is not the same as laying into someone because they're slow at their job, and berating a cop for punching a kid during an arrest is nothing like making sailors blush by yelling at a parking cop who's writing you a ticket because it's a minute past what you paid for.

Will some folks try to get fines issued as an obvious overreach? Yep. And that's what courts are for.

What's the bug? "Getting a copy of the sandbox files you can already ask for in a session"? Not a single file here is sensitive or meant to stay hidden, it's just the sandbox. You set those up yourself if you're running local models, too, there is no secret sauce here.

This is not a font in any way of the word, this is a typesetter. It would be a good idea for the author to change the title, because right now it's not just clickbaiting, it's flat out lying.

And on an unrelated website note: don't have a mystery toggle. If you want to offer light and dark modes: awesome, but actually say what the toggle's for either through iconography or by using text.

I mean, with a completely new C-suite gutting the company, that sure isn't the only thing that's changing.

how about "just turn off your company if you're so worried about AI instead of immediately suggesting we use it to judge people's lives and livelihoods"?

Indeed, it is extremely clear: by not saying "manufactured in Japan", the words "developed in Japan" tell you that they drew up the designs for the CPU in Japan, and then sent those designs off to a fab outside Japan for actual manufacturing. Then they bring those CPUs back to Japan, so that the server can be manufactured in Japan even if the server components are not.

That manufacturing step may change in the future, but right now that CPU is not "Made in Japan", it's only "Designed in Japan".

The main.css file it imports dates itself to March 9 of 2005, and is housed in an "ancient history" section of the website that covers everything before October 26, 2010, so: "sometime between those two years" =P

Or they need the pay. It's all well and good to go "they could just leave" but then what? Spend 6 months looking for a new job only for everyone to go "sorry, the hundreds of thousands of layoffs from every other highly skilled tech workforce beat you to it"?

First off, RAM is not app size, and second, the point of having RAM is literally so it's there to be used. Sure, Chrome is absolute nonsense, but Electron is not Chrome, and an Electron app using 300 MB in memory where data needs to be uncompressed and directly accessible when your computer (including your phone) has gigabytes of the stuff to work with is just... irrelevant? That's pretty much pretending there's a problem for the sake of wanting a problem.

And yes, not using electron will use less memory, which is an excellent reason to go "we're not using Electron". But there's a difference between "We want to use as little memory as possible" and "300MB of RAM on a system with 8 gigabytes of the stuff is a problem". The first is an excellent call. The second is nonsense =)

It's funny how folks can't even get that number right. Depending on how much you care to optimize, Electron adds 50 to 80 MB to your application. Those multi hundreds of megabyte apps? Yeah that's not because of electron, that's things like "we couldn't be bothered to actually think about the assets we bundled in". 100 uncompressed 16 bit PNG? Sure why not. 20MB worth of fonts because we don't like the built in ones and no we've never heard of subsetting? Let's go. 50MB worth of .json data files that we couldn't be bothered to gzip first? Who's going to notice!

Electron is way bigger than an app needs to be, of course, but those giant apps that you hate, 250MB just for a health tracker? That's not electron being the problem.

Those include the name of the company and actively marketed product. If Google rebranded to Winklemoops, and Android get renamed to Callithing, then the "Google" and "Android" trademarks would eventually expire due to trademarks being contingent on actual use. So yeah, "Google Wallet" and "Android Pay" would eventually become perfectly valid names for someone else to claim.

And Twitter being renamed to X is literally that: the company and product name were changed, and both the company and product no longer uses that original name for anything other than to call out "formerly Twitter". That is not "use" for the purposes of keeping your trademark.

Surely by literally saying "formerly Twitter", this is an admission of non-use, thus invalidating the trademark on the term as it is not just "not used for anything" but is explicitly being distanced from by X in writing.

I understand your frustration, it can be hard to hear that other people's experience of a technology is so different from your own that you cannot relate.

I have misbehaved in this fashion for many people across the full spectrum from casual users to highly experienced software engineers with millions of social media followers, so the statement that it's similar to making a joke about a calculator misadding two numbers because a stray beam of solar radiation flipped a bit at least for my part is not true.

Would you like me to start using bad English and doing things you never asked me to for your sessions, too? Just say the word.