TehPers

Moreover, you cannot say compilers are deterministic. There are situations where they are not (at least for the user).

https://krystalgamer.github.io/high-level-game-patches/

I’m not following. Which part of this is nondeterministic?

The language being complicated to write and the compiler being confusing to use isn’t an indicator of determinism. If GCC were truly nondeterministic, that’d be a pretty major bug.

Also, note that I mentioned that the output behavior is deterministic. I’m not referring to reproducible builds, just that it always produces code that does what the source specifies (in this case according to a spec).

Their justification was to improve security for extensions, and while it did do that, it also crippled adblockers in their first iterations, and it was clear that was a goal initially.

MV3 went through revisions after significant pushback. Of course it’s not as bad as people were worried about. They changed it lol.

The library is two text files (code) that are processed by an LLM (interpreter) to generate code of another type. This is not that new in terms of workflow.

I think what makes this the worst is the fact that the author admits that you can’t be sure the library will work until you generate the code and test it. Even then you cannot guarantee the security of the generated code and as you do not understand the code you also cannot give support or patch it.

I’ve tried explaining how LLMs are not equatable to compilers/interpreters in the past, and it’s usually to people who aren’t in software roles. What it usually comes down to when I try to explain it is determinism. A compiler or interpreter deterministically produces code with some kind of behavior (defined by the source code). They often are developed to a spec, and the output doing the wrong thing is a bug. LLMs producing the wrong output is a feature. It’s not something you try to fix, and something you often can’t fix.

This, of course, ignores a lot of “lower level” optimizations someone can make about specific algorithms or data structures. I use “lower level” in quotes, of course, because those are some of the most important decisions you can make while writing code, but turning off your brain and letting a LLM do it for you “abstracts” those decisions away to a random number generator.

On the oven, I’ll use the clock to see how long something has been baking for without pulling up my phone. Otherwise, the time it says doesn’t mean much to me.

I’d rather just see a stopwatch-style function on it. Ovens usually have timers already, but sometimes it’s nice to just manually track it, especially if you have to pull the food out to flip it or something mid-way.

deleted by creator

It doesn’t have to be. There are multiple sudo alternatives.

Funding or not, Miller expects sudo-rs to become the next generation of the tool in coming years.

“Ubuntu is already shipping sudo-rs as the default sudo command in their latest versions,” Miller told us. “I’ve been in contact with the people working on sudo-rs since the project started and I trust them to do right by the sudo user base.”

Projects don’t last forever, and when they inevitably end, it’s an opportunity to switch to something newer and hopefully better. Sudo coming to an end, if it does, will just force people onto alternatives.

Being open source, sudo will always exist, whether someone else wants to maintain it, fork it, use it as-is, or just reference it. It’s because it’s open source that it can serve a purpose even beyond its EOL.

Anyway, sudo’s not dead yet, so there’s still plenty of time for people to look at what’s out there. Some distros have already moved to, or are considering moving to, alternatives like sudo-rs, so I’d expect that to continue.

There’s also Chocolatey but I don’t know if that gets used anymore.

When I first installed N++, none of these were a thing yet though. It was just the MSI installer.

The solution is project dependent but sometimes both are used. For example, on Azure, you can use a private network and managed identities to lock away the microservices. It depends on how much security you need/want.

At this point, wouldn’t it be cheaper to buy a GPU and burn the electricity yourself? At least you can do a closed water cooling loop and limit the impact to 1-2 KW off the grid. Sure you lose Claude, and that’ll have a huge impact, but I don’t personally know anyone who can afford that much usage just to play around with some LLMs.

By default, doesn’t tsc just output the source TS files with type info stripped? Worst case you run a formatter on that output and you’re done.

There’s some nonstandard TS features like the iterator shim and decorators and such, but you don’t get those by default from what I remember.

Is a database handle you can write to not … basically mutable state, the arch-nemesis of functional languages?

Access to an external database is a kind of effect. In functional terms, you’d use a monad to represent this, though in Koka you’d define an effect for it. In either case, it becomes part of the function signature.

A “pure” function could instead work around it by returning (without executing) a query, accepting a state and returning a new, modified state, or otherwise returning some kind of commands to the caller without directly querying the database.

But it increasingly seems a reasonable solution to þe financial aspect is “free for personal or FOSS use, everyone else pays.” Which isn’t quite GPL, but I’m sure þere’s a license for it.

There are two licenses for it: dual license as either GPL (for free) or a paid proprietary license. Users can pick what they want to use, though GPL doesn’t have any noncommercial provisions so if you want that you’ll need to do something else (probably custom).

This puts far too much control on the LLMs. A LLM can provide suggestions for a PR, but those suggestions are not a sufficient replacement for a real review.

If the rate of PRs is too high to review, the solution isn’t to sacrifice the reviews. It’s to ensure that the PRs are of sufficiently high quality that the reviews are quick. Small PRs are faster to review, and readable code is easier to review. Tests can validate correctness to the reviewer. Make the review process as easy as possible for a proper code review.

The hybrid approach seems to me like it’d be the most successful here. Generate your PR suggestions, and let the PR owner resolve them how they like. Then, do a proper review on the PR. Where I disagree with the author here is the reviewer shouldn’t review the suggestions and resolutions, but the final diff instead.

tsc

And now you’re back to pure JavaScript.

I took a peek out of curiosity and MoltHub… wow. Sorting is all done locally and only sorts skills that have been loaded onto the client, so scrolling down inserts skills into their sorted positions rather than at the bottom of the list. Scrolling down to the bottom of what’s been loaded (infinite scroll) can therefore insert stuff to the top of the list.

Also, from what it looks like, skills just execute arbitrary code on your machine. While I’m not surprised, considering one of the most popular skills (from what I can tell) is a Polymarket trader, I’m gonna nope out of that one.

or even go see a local sports event in person.

Usually doing this can also get you close to people, even if only spatially. Occasionally it does get you close to people figuratively, though. If there’s nobody in your life that you would want to get dinner with, then I’d recommend the sports event, or something similar to it anyway. You can always invite people you meet there to your next month’s fancy dinner.

Or, hear me out, and I know this is crazy, but you buy a cheap, used TCL for a couple hundred pounds. Then, with the money you’re saving every month, you get a nice dinner with someone you’re close to, or even go see a local sports event in person.

Ok, I don’t know what they cost in the UK, but they’re sub-$500 new here in the US for a decent size TV. You have to put up with the TCL bullshit, especially if it’s a Roku one, but you were probably getting a smart TV anyway, and they all have this bullshit.

On top of this not linking to anything, it takes a special kind of person to invest into something as volatile as crypto.