Programming

However, there are some important features that WinSock just doesn’t expose. […]

Rust’s current async ecosystem is built atop a particularly cursed concept. It’s an unstable, undocumented Windows feature. It’s the lynchpin of not only the Rust ecosystem, but the JavaScript one as well. It’s controversial. It’s efficient. […] Without it, it’s unlikely that the async ecosystem would exist in its current form. It’s called \Device\Afd, and I’m tired of no one talking about it.

“Jujutsu (jj) is a version control system with a significantly simplified mental model and command-line interface compared to Git, without sacrificing expressibility or power (in fact, you could argue Jujutsu is more powerful). Stacked-diff workflows, seamless rebases, and ephemeral revisions are all natural with jj [...]”

Part 2 of the series is out and is here.

Well, I hope you don't have any important, sensitive personal information in the cloud?

prizes include 11 hours for the Smolhaj, 5 hours for a 128gb thumb drive, 3 hours for Geometry Dash, and 21 hours for 6 months of Mullvad. like i said it's just like a rewards program lol

Today I published an update to my remote-docker project.

The purpose of this project is to run Docker on a remote computer while providing container access to specific parts of your local filesystem with X11 support.

For example, you can use this to run your browser inside a container and only give it access to your ~/Downloads folder.

Access is over SSH (and SSHFS) and Docker is not installed on your workstation, just a few bash scripts.

Feedback (and patches .. Ha!) welcome.

Have fun!

O

cross-posted from: https://lemmy.bestiver.se/post/526967

Comments

I am a senior java developer in the cloud/distributed arch/ microservice area.

I've touched on golang in the past, but not learnt it in any formal/extensive way.

I see it cropping up in many java/microservice positions, and I'm curious if this is at some point going to overtake java in my area.

The current benchmarks seem to suggest that if autoscaling is key to your services, golang is the way to, well, go.

I looked at the job market and it doesn't yet seem to have taken over, but I'm curious how this is likely to play out over the next decade and if quakus for example is likely to become more competitive against golang. Interestingly, golang specific roles on average pay less than java ones in my area.

Let me know your thoughts or if you have any good articles / content on the subject.

Archive link: https://archive.ph/A7LI4

Marianne Belotti has worked at large institutions with modernizing decades-old code bases. She is author of the book "Kill it with Fire" [review].

From that book's author bio:

Marianne Bellotti has worked as a software engineer for over 15 years. She built data infrastructure for the United Nations to help humanitarian organizations share crisis data worldwide and tackled some of the oldest and most complicated computer systems in the world as part of United States Digital Service. At Auth0 she ran Platform Services, a portfolio that included shared services, untrusted code execution, and developer tools. Currently she runs Identity and Access Control at Rebellion Defense. She can be found on most social networks under the handle bellmar.

Cody, one of the first few decently good AI assistants that were well integrated into VSCode bit the dust just recently as the greedier and greedier Sourcegraph direction decided to switch to the completely Enterprise (read proprietary) "solution" Amp.

With this commit, another notable project by them goes down, first was their signature code search engine, now this, I just feel sorry for everybody who contributed and now will see pretty much all their efforts rendered meaningless, it was already apparent by how Sourcegraph approached Search sunsetting how much they care about open source, but I'd say this seals the deal even better if you needed insight into whether to trust them or not.

I think what's left by them that might be useful still is the zoekt library and a few other minor repos they have, but they're nothing compared to the impact of the other two.

Things like these make me question how we can just buy in to projects using non-copyleft licences, it's a time bomb, especially with corporate driven software and I see many developers fall into that trap, that in an endeavour for perceived simplicity, will choose Apache, MIT, Unlicense (pls not this one 🥲), or what have you and not care.
What people see as pragmatic in open source is really just a conclusion that comes from the point of view of the maker, rather than the community

Cool even if you're not interested in learning Scheme. It has some neat features.

Code as data? 😵‍💫

I thought of this recently (anti llm content within)

The reason a lot of companies/people are obsessed with llms and the like, is that it can solve some of their problems (so they think). The thing I noticed, is a LOT of the things they try to force the LLM to fix, could be solved with relatively simple programming.

Things like better searches (seo destroyed this by design, and kagi is about the only usable search engine with easy access), organization (use a database), document management, etc.

People dont fully understand how it all works, so they try to shoehorn the llm to do the work for them (poorly), while learning nothing of value.

A bit old but still interesting

Not yet released unfortunately:

https://kyber.media/

So, I work in a medium sized team and earlier in this year, our team helped another that was behind in some tasks that all of us need to complete together.

After this, that team always asks for help from our team for untested things from their side and the worst part is whenever something breaks on their side, it breaks for a lot of people (like us) too, and they break a lot of stuff, simply not testing anything, no unit tests, no integration tests, nothing, they just throw broken shit out of the door.

This happens even to the things we made at their place, something's up with our code? They changed it. It doesn't seem to matter if it's adding 2 lines to a sql query, they added an extra comma and didn't test, they changed the batch processing? Now the process returns a broken json with different fields than the Enum expects. Yeah, they changed the value of the field that was ALREADY working for no reason and didn't test it.

I'm pissed off, told my coworker that it's their problem now, but the problems always come and the boss call us to help. This is very frustrating for us and for other teams too, even today another boss was talking about them breaking things in another system that we and they interact.

Their boss seemed to just want to give work for them, even with these problems coming back. The outsourced people work better than them, but you know, they are outsourced and the not so competent team is in house, so they can do nothing.

What can I do? Just saying no when the problems come? Talking to their boss?

An oldy but a goody.

I'm currently writing a CLI tool that handles a specific JSON data format. And I also want to give the user to get a slice of the item array of the file. It's a slice in form of --slice START:END through commandline options. So in example --slice 1:2.

1. Should I provide a 0 based index for the access or a 1 based index? In example --slice 1:2 with 0 based index would start with the second element and with 1 based index it would start with the first element.
2. And would you think its better to have the END to be inclusive or exclusive? In example --slice 1:2 would get only one element if its exclusive or it gets two elements if its inclusive.

I know this is all personal taste, but I'm currently just torn between all options and cannot decide. And thought to ask you what you think. Maybe that helps me sorting my own thoughts a bit. Thanks in advance.