skysight-inc/HackerNews huggingface dataset:
A preface: I use GNOME and KDE on separate devices. I have tried i3 and intend to return to it when graced with more time to customise it. Importantly, I used GNOME before GTK3 happened.

I mention the above as preface because I see these kinds of posts on this website a lot and they are very misleading, and I believe I have the credentials to explain why.

If you skim the original article you could be forgiven for thinking that it is a well researched and justified piece of writing, but I would like to challenge that. In particular, I note that a lot of 'evidence' for the claims of GTKs downfall are hinged in the author's preexisting expectations (and bizarre tangents - who gives a shit about title bars one way or another in a conversation about software maintenance? Scope pls).

One very revealing assumption by the author is the idea that a major release of a community project such as GTK3 should be free of bugs. This seems very obvious to an end user. 'Of course a major release should be stable! What are you saying? I need my servers to be reliable so I can feed my kids! Not everyone lives in fantasy land like you, plaguepilled!'

But there are actually two assumptions being made here. The first is that major releases of FOSS should be free of bugs and not corrected with time, and the second assumption is that this is no harder to accomplish than for a commercial entity.

However, crucially, the open source software community has had a huge shortage of maintainers for at least a decade now. Look up your favourite utility, then look up the team supporting it: often it is one person who is very, very over it. This can contribute to the phenomenon of fixes that come after the major release, not with it.

In fact, this single fact can explain why major projects that 'weren't broken' seemingly 'choose' to self sabotage. The GNOME team are not stupid. They are heavily under-resourced. The same can be said for KDE and even the Linux kernel teams. If that bothers you, it is far more productive to actually contribute your time to fixing the issue than simply describing it while waxing lyrical about how all these modern devs have simply 'lost the way'.

But I am here to contend that the idea of flawless FOSS is itself bizarre. Wealth inequality is a major issue in 2022 and proposing that the existing body of skilled software engineers should provide enterprise level software, consistently, without pay, is insane. If you care about software support and are not paying, and you do not yourself write FOSS software, you are at best a hypocrite, and at worst attempting to exploit people.

I am a fan of FOSS and want it to be better, but this article is not the way to that future.
How is a traffic light ambiguous? The stop and go lights are physically distinct lamps. The top light means stop, the bottom light means go.
Isn't this a very standard method of exploitation that competent pentesters test for?
They plan to deprecate scp the protocol, not scp the tool, which will use SFTP under the hood.
The protocol is being deprecated not the scp command. It's been reimplemented over sftp. They have had to handle wildcard/glob expansion, and how scp tried to deal with it.

TL;DR it's just the same command, mostly, for now.
Every time I pay enough attention to an OpenSSH release that I trick myself into reading some of the code, I'm left smh in disbelief that I actually rely on this software still.
My setup is FAR from cheap: DENON 13 channel AVR, Monitor Audios all round, and KEF upfiring Atmos, all in a nice 7.1.4 setup (with a 100" projected image).

I went with upfiring, as I didn't want to hack loads of holes in the original ceiling of my 90 year old house. Yeah they are not as good as in-ceiling speakers, but I wouldn't say upfiring is always for 'cheap setups' - sometimes you have to just live with the restrictions you have.
Thiel: Bitcoin will 'never be' controlled by government, unlike 'woke companies'
scp the protocol is being replace by the sftp protocol, scp the tool will use that new protocol
This whole discussion here is somewhat weird because everyone keeps thinking about shitty soundbars and headphones. Dolby Atmos and DTS:X on a home cinema system with decent and large speakers is amazing and noticably different than simple non-object based surround systems
>And yet not very many people think we’re in the middle of a second housing bubble.

Yes. Many people think we're in the middle of a much larger bubble across the whole unsustainable economy.
They ditched the concept about ten years ago. Being out of the loop I had to look up if APFS even supported them anymore, and in doing so, found opinions on two ends of the spectrum: the concept was the best thing ever, or one of the most detestable features. I guess no one really understood how to use them anymore and added to it's demise.
How to investigate memory usage of your Rust program
Computing had always been cringe, but exemptions are made so long it makes money, by minimum amounts necessary. From Apple I to Amiga to MacBooks in Starbucks it's all it, but no one calls it for Tim Cook while he turns aluminium into gold on stage.
Congratulations. Zas looks very cool, I will definitely try it out and see if it can fill the (large) gap between Visual Studio Code and a full-featured IDE like Goland or CLion for me.

Can you please give an outlook in which direction you plan to go with Zas Editor in the future? Is the plan to target only a few specific programming languages, like currently Golang and Rust, or do you want to become a generic code editor like Visual Studio Code or Sublime Text and support a large number of languages and formats?
The scp protocol is being removed, but the scp command you find convenient isn't going anywhere. So that convenience ought not to change, except that now the quoting does what you probably expect, because it's just a local command and so nothing weird is happening.
I love this thread, pseudonymous circle of unjustified likes or dislikes of a specific technology.
the only snag about this plan is that the old `scp` tool works with any server, whereas the new tool will require additional configuration on the server to enable SFTP.

It's not enabled by default in some distributions and many "how to secure your server" guides recommend disabling it/keeping it disabled due to the best practice of only enabling necessary services.

This will break `scp` for many corporate cases (where arguing that sftp is necessary is an impossible fight)
I'm somewhat of an old fart, but rsync(1) has worked well for me. It integrates well with ssh on both sides, using ssh channels to execute the binary on the server side and transporting data nicely back and forth.

It isn't suited for millions of files, but neither is scp.
I think there's a target market segment you're missing here and it's hinted at in the lede:

> Easily develop software, view code or take notes on the go.

iPads are very popular with students in markets where they can afford them, and tools like these are a great fit for them.
> Only support services that aren't blatantly trying to buy their way into becoming a monopoly and abusing their locked in customers.

There are no such services. Everything that gets popular goes for abuse and lock-in and often they only start with that after they already have become wildly popular. There is nothing you can do against it.
In 27 years, I've had exactly two jobs where I didn't have Linux on my desktop, for a total of 5 out of those 27 years. In both cases, I still did all of my dev work on Linux.

It boils down to what kind of jobs you look for.

> So yeah, running cloud services doesnt require sysadmin skills, unless you assume copy pasting from oficial documention "sysadmin skills".

If that's the extent of how you're managing your cloud setup, then I could equally argue running bare metal servers doesn't require sysadmin skills either. When I did contracting, a large part of my income was to come in and clean up after people had relied on "copy pasting from official documentation" as a substitute for actual ops.
It is not clear what kind of dress the fallen man had in comparison with the enemy (whose dress is obscured by some kind of shield).

On the other hand, while the enemy fought with a spear, the fallen man had both a sword and a scabbard of exactly the same type as the victorious fighter.

So based on the weapons, it seems more plausible that the fallen man was a comrade.
I'm pretty sure scp isn't a protocol. It is just a tool that relies on doing a request for execution over the regular ssh2 protocol.

I've written a few custom ssh servers and you don't really need to do anything to them to support scp.

sftp uses the sftp subsystem. scp just uses regular ssh requests and transports data over the ssh channels.
"Why can't we have a language that compiles to highly optimized JS?" is definitely something that has crossed my mind, especially in situations where I reached for faking structs with TypedArrays. As soon as that gets more complicated than something like an array of x,y,z points things get difficult (not to mention almost impossible to debug) really fast.

I suspect that if you could come up with an easy way to express a large tree really efficiently in a TypedArray in a relatively generic way, that you already will do better than most attempted solutions here.
> A few years ago, 2013, there was a study in Germany where a lab had tested various espresso machines and found lead.

My memories are fuzzy and incomplete, but I remember that nothing ever happened because there was a big uproar from manufacturers.

Tangential: let's not forget the whole dieselgate scandal of VW and certain other European car manufacturers.

I mean, they use all their engineering prowess to come up with this?
sftp, rsync, scp using the sftp protocol in the background (which is now the default).
The scp tool continues to exist, but implementation switches to SFTP as protocol from SCP protocol.
Glorified Goto spaghetti
> As an aside, keeping language and OS versions up to date becomes a development task rather than an ops task when running Docker + ECS.

It's a development task with a proper bare metal setup too.
I don't question their team. It at least sounds mightily impressive (just checked). My problem was, that this Form of marketing claim put me off.

Might be a cultural thing.

I wasn't even interested in spending more time than looking at around 5 pages to see if the claim might be substantiated somewhere. It wasn't obvious so the heuristic is that it is not substantiated.
Yep, it's inspired by COG as well as MBTiles, hence the name. Key differences are:

* like MBTiles it's agnostic to what individual tiles are. You can store vector data as SVG, Protobuf, raster PNGs, JPGs or even raw digital elevation models.

* It's not backwards compatible in the same way Cloud Optimized GeoTIFF is.

* It has a recursive index structure to avoid needing to load in huge indexes at once for large datasets (hundreds of millions of tiles).

* It is designed for remote HTTP range reads. If your application can instead directly access a filesytem, like on a mobile phone, MBTiles, which uses SQLite, is a more established solution.

The specification is open source on GitHub https://github.com/protomaps/PMTiles and is still evolving in response to user needs. I've created direct client support for Leaflet and MapLibre, and plan to work on OpenLayers next.
I used to think that social rituals were bullshit, but I've completely changed my mind. I think they are just often done poorly and distract the team from what is important. I'm sure there is room for improvement and YMMV, but our current process is working really well for us:

- As some context, we use Basecamp's Shape Up to deliver features. This prioritises independence, async communication, and deep work. Engineers and designers are largely free to manage their active projects to how they see fit (managers provide context).

- Team social activities only happen on Mondays and Friday. Tuesday -> Thursday are reserved for deep work.

- We found that mixing social and work meetings didn't work (i.e. a weekly kick-off where people both talk about their weekend and their priorities). Instead, we have a 100% social coffee video call on Monday mornings with some jazz. Weekly work updates happen async and are project-dependent.

- On Fridays afternoons we have a quiz or a board game. We like doing it later afternoon on Friday, where deep work is less likely to happen. We also have an async social check-in with a different prompt each week, where you can share some experiences, pictures of a holiday, etc.

- Quarterly retreats where we get the team together. We do a morning session and an afternoon session every day, with the rest of the time unstructured/fun.

Things are avoid:

- We avoid stand-ups which devolve into people listing out what they did yesterday - instead, we encourage async self-organization

- We try and back to back meetings to avoid context switching and 30m-2hr deadzones

- We discourage arranging calls just to organize thoughts (I was bad at this myself). In our experience, communication is higher fidelity if it is written up in message threads on Basecamp. Video calls are really only used for 1:1s, social meetings, demos, or regrouping in the context of an active project.

- We got rid of Slack. Active projects have their own chat rooms, but the rule of thumb is: presume anything not in a forum thread or document is ephemeral and will be lost forever.

We have started putting together a lot of our rituals and culture together in our handbook (https://handbook.datapane.com), so would love any feedback.
Great article, but that was probably the worst experience I’ve ever had on mobile reading an article. Page kept sporadically reloading and jumping back to the top. Seemingly if I scrolled down in the wrong manner or clicked something it would trigger a reload or jump to the top. What a dumpster fire of a website.
So I can't set up a headless Pi any more without using that imager tool?
Another option people may want to consider is hosting a version of Code Server[1]. I do this with my iPad Pro and it has been incredibly convenient.

I even have it configured so that ports can be routed to via my domain, meaning I can do web development with a local server on port 3000 and view it live at 3000.my.domain.tld.

1: https://github.com/coder/code-server
I think our daylight savings started around that day!
Very true! Apparently not such a nice person, but still an amazing author.
>I guess quit your job for a year and build your own home!

Who can build a house in a year by himself? Even with a group of skilled professionals it can take longer. Plus you'll be on zero income for a whole year.

>Maybe get into the home building business altogether.

Easier said than done. In Europe this is a credentialized profession so for insurance purposes not everyone can just roll up their sleeves anymore and just start building houses like it's 1886.
I just opened a 4GB JSON file in VScode, it took a few seconds to load, but it is fast enough for me. Syntax highlighting disabled itself, but searching text works.
I think you're extrapolating that far beyond the specification.

Honestly I've actually tried to sit and write code on an iPad. I forced myself to exclusively use one for 2 months. It's one of those things where it's entirely the wrong tool for the job. Casual note taking perhaps but that's about it.
These days, your ISP would (hopefully) give you at least a whole (static) /56, so you can always reserve some prefixes for your not-really-home networks ?

https://www.ripe.net/publications/docs/ripe-690#4-2-3--prefi...
We Will Fix Climate Change
Space was weaponized from the start. The impure usurpers are the ones who look at how to scienceize space weapons.
Because it is trendy.
>paint at best a murky picture

Going out of your way to add something that you wrote is very clearly a more intentional and conscious act than failing to remove something that someone else wrote. The picture is crystal clear.

>they were remarkably incompetent in crafting their license

Perhaps. Irrelevant.

>It seems to be a bit of a stretch to say the courts must interpret it as if it's the license they should have written

That's the only possible resolution mechanism when someone writes a self-contradictory contract. Law is not code. Intention matters.
Hypertrace – Jaeger alternative for distrubuted tracing
An old firm I worked for had their router switch in the toilet. Not literally /in/ the toilet you understand, but above it, on a shelf. Was that really the only solution they could come up with, I wonder?
What about the teachers and all other staff at the school? Or everyone those children will run into, like parents, siblings, grandparents, friends, etc.? Even if the majority of them are healthy and under 45, some won't be and would require hospital treatment. And that's a severely limiting factor on how much Covid a health system can bare - in many countries that was stretched to and beyond it's limits. Now thankfully the latest variants are much more benign so that's not really a serious risk, for now.
Did you try Beorg on mobile?
React 18 is in fact throwing Promises for the new implementation of Suspense working on Server Side Rendering.
I found it brilliantly elegant.
Throwing a promise in that context means "I'm not done yet and you should display a fallback"
Can you tell why that is? Did you find the OpenSSH source code especially bad? I am under the belief that OpenSSH is a really high quality, security focused software project.
Anecdotally I am a 30 year old male who is usually only ill for about a day or 2 every year. I had COVID for a couple of days and then a week later after recovery a started getting this super-dry cough. This stayed with me for 2 months, first of which was so bad I could barely sleep until I got a codeine-based cough syrup.

On the other hand I was also considering what our politicians did to the society keeping them locked up in their rooms and not training their immune systems on a regular basis which usually happens with normal interaction.
We do the "post a fun photo" thing through Geekbot but for me the best ritual that helps in many ways is that we do work outs on Zoom 3 times per week.
Besides the obvious health benefits, it is a nice way to bond the team.
Why are there so many different hammers? Why don’t we use a single handle to which you can attach different heads, maybe even click on additional weight to a head, if needed?

That works for drills and drill bits because it’s relatively easy and because we don’t want to have 20+ drills each for a given drill bit, but even there, it only works to a given extent.

We have different versions of tools not only because we can, but sometimes because they work (sometimes slightly) better for the job at hand.

Also, editor shortcuts often are fairly standardized on an OS and for many users keeping the same macros isn’t worth much because they don’t have many. That makes the special features worth switching sooner.

In some sense, heavy macro users have climbed a hill that it’s hard to get off, if it turns out to be only a local optimum, and they spot a significantly higher hill.

Now, why do we have more editors than, say, spreadsheets or movie editors? I guess that’s because programmers use them more, making them think they can do better.
Capturing and redirecting DNS traffic is not difficult. You can do it yourself to force smart devices with hard-coded DNS settings to go via a local resolver that filters ads/stalking, so I have no doubt there are ISPs doing it to their customers to keep control for the purposes of tracking and NXDOMAIN hijacking.
The big difference between malicious behaviour of the ISP vs malicious behaviour from all those example companies you mentioned is that I can choose not to use Netflix/Google/ESPN/..., while I can't choose ISP. So yes, I need DoH to protect me from my ISP (and no, full blown VPN is not an option, too many compromises).
On the contrary - when you create a user using useradd, it initially has no password, and so cannot log in.
> Wow. Listen: code written in languages heavy with sigils and shorthand are hard to understand, read and most importantly: maintain.

As someone who maintains a 145k line Rust codebase all on his own, I have to hard disagree on this one.

Once you get used to the syntax it just blends into the background and becomes a non-issue.

> This adds a mental load which is -- as clearly visible from above -- is totally unnecessary.

Totally unnecessary? Okay, so how would you do the following with the sigilless syntax (and disambiguate between them):

- Specify a unique reference? (`&T` is shared, `&mut T` is unique)

- Specify a lifetime? (`&'a T` is a reference to T with lifetime `a`)

- Specify a raw pointer? (`*const T` and `*mut T` are const/non-const raw pointers)

- Specify that the argument is moved into the function? (just the raw type `T`)

People have been trying to come up with a better syntax for Rust, and AFAIK so far nobody has been able to do it. There's always a tradeoff somewhere that ends up making matters worse than what we have now.
So did Obama for withdrawing troops from Iraq and sending them to Afghanistan. Sometimes they get it really wrong.
Italy, being Italian, not being fiscally resident somewhere else for more than six months.

Esterovestizione is the specific term for that kind of fiscal crime.
> If you don't know a project's maintainers and you trust GitHub then this model lets you verify the maintainers' work by looking at the source,

I'm not sure I follow.

GitHub is basically a glorified git repo.

So I still have to trust the people who do the git push, no ?

If so, then I fail to see how you can do better than git PGP signing ?

git PGP signing enforces integrity at the basic level, so you've got a chain of signed git commits.

I don't understand the "trust" in saying, "well, we've got too many maintainers to track PGP keys, so instead anybody can commit and we'll abstract the trust away to the build-level where we trust Github to build it without tampering, and we trust someone else to sign it" ... because that's what I read it as.
Well that was fast!
* Yes, the serverless part is a CDN accelerator for any tiled data, as long as you can get your own map data into PMTiles format. I have tested with azure functions but it's not as mature as other platforms yet.

If your several map apps are part of a single organization, it should be fine. I'm happy to discuss this more if you email me at brandon@protomaps.com.
Namecheap's DNS provides dyndns support. It's now just an add-on to your DNS or domain name provider.
Fair point!

I guess it's a one-way function given only the key as input with a fixed ciphertext.

Incidentally if you use AES in a AED mode (like AES gcm) then it would be a one-way function but that is more about the MAC.
I don't think we do any of this... we have a 24/7 open group video-call, people can join and leave when they want to have a chat, or want to ask something to the group or are looking for assistance. In depth technical talks will then usually migrate temporarily to a second/third channel. We do our daily standups in the main channel to keep it alive and active.
Besides that we have many (signal) text-channels for every group/team/technology, so people can get contacted easily.
Are you people hiring?
How to control the metacognition process of programming?
Eslint with standardjs in js is so great, set it up and it will fail if you throw anything different from an error.

https://github.com/standard
Recommendation: Read “1177 B.C.: The Year Civilization Collapsed” by Eric H. Cline https://press.princeton.edu/books/paperback/9780691208015/11...
What does it have to do with 'Putin'?

It is not Putin's war. It is russian attacking ukraine. With elected leader, with overwhelming support. Every russian is responsible for every atrocity. Russians never was good in takin responsibility for their actions, always blaming 'the government' they elect and support. I have enough of this shit.