j1elo

I would always go to the official docs page for the needs I have, and use their HTTP library (or any other). It removes decision making, having to ensure good quality practices from lesser known libraries, and risks of supply chain attacks (assuming the root stdlib of a language would have more attention to detail and security than any random 3rd-party library thrown into github by a small group of unpaid devs)

Only when it falls short on my needs, I would drop the stdlib and go in dearch of a good quality, reputable, and reliable 3rd-party lib (which is easier said than done).

Has worked me well with Go and Python. I would enjoy the same with Rust. Or at a minimum, a list of libraries officialy curated and directly pointed at by the lang docs.

I just grabbed an Android remaster of "Broken Sword: Shadow of the Templars", a 90's point-and-click adventure that has been added a hints system which pops up automatically after a timeout of the player not progressing.

This can be set as far as 1h of being stuck. Can also be 5 minutes. But by default it is 30 seconds.

My inner kid was screaming "that's cheating!" :-D but on second thought it is a very cool feature for us busy adults, however it's sad the extremes that gamedevs have to go in order to appease the short-term mindless consumers of today's tik-toks.

But more seriously, where's the joy of generating long-standing memories of being stuck for a while on a puzzle that will make you remember that scene for 30 years? An iconic experience that separates this genre from just being an animated movie with more steps.

I couldn't imagine "Monkey Island II but every 30 seconds we push you forward". Gimme that monkey wrench.

TFA and this comment just made me have this thought about today's pace of consumption, work, and even gaming.

Wait a moment, you just gave me an idea for a product

> went closed source and started injecting adware into checkout pages ... [and] geolocation tracking.

Maybe we should resort to blame and shame publicly this sort of actions. DDoS their servers, fill their inbox with spam, review-bomb anything they do. Public court justice a la 4chan trolling. Selling out is a lawful decision, of course, but there is no reason it shouldn't come with a price tag of becoming publicly hated. In fact, it might help people who are on the verge to stay on the ethical side of things (very ironically).

I'm just kinda joking (but wouldn't hate it if I was rugpulled and the person that did it got such treatment)

In IPv4 you only need to transmit IPv4 addresses. If the "cannot be" in parent post is referring to the exact byte disposition in packets, then I go the other way around to claim that I agree. Because the only way that a UTF8 character can pretend to be ASCII is because ASCII didn't use all of the 8 bits in a byte to begin with. Only way to have something similar in this case, would be that IPv4 didn't use all of the allocated bits for addresses... Which is not the case.

What I argued was that IPv4 could be embedded into IPv6 address space if they had designed for it. But I agree, that the actual packet header layouts would need to look at least a bit different.

Why not? Sincere question. As a very superficial idea, if we go back to the drawing board, for example we could decide our new cool concept of address to be an IPv4 + an hex suffix, maybe at the expense of not having a humongous address space.

So 10.20.30.40 would be an IPv4 address, and 10.20.30.40:fa:be:4c:9d could be an IPv6 address. With the :00:00:00:00 suffix being equivalent to the IPv4 version.

I just made this up, so I'm sure that a couple years of deep thought by a council of scientists and engineers could come up with something even better.

We don't need to be communicative at all times. But don't romanticize it either; we did what you say because we had to, whether we wanted or not. Not having any chance of correcting course or being more flexible is not a cool thing of the past, it's a limitation of how things were. That you find confort on it, is a different thing than it being better or worse... it just was.

As if it would make sense that spending 2hrs relaxing on the beach or gardening your orchids would cost $400 to you. Money not made is not money spent. If you were doing a hobby project for learning, you were not going to be working during that time anyways, so your hourly rate doesn't matter.

What a messy and frankly, absurd situation to be left in. To fork a project in order to provide a tool through Pypi, only to then stop updating it on a broken version. That's more a disservice than a service for the community... If you're going to stay stuck, better to drop the broken release and stay stuck on the previous working one.

A nitpick to your nitpick: they said "memory location". And yes, a pointer always points to a memory location. Notwithstanding that each particular region of memory locations could be mapped either to real physical memory or any other assortment of hardware.

Well obviously that would happen mostly only on the biggest business scales or maybe academic research; one example from Nvidia, which showcases Apache Spark with GPU acceleration to process "tens of terabytes of JSON data":

https://developer.nvidia.com/blog/accelerating-json-processi...

Whenever you have this kind of impressions on some development, here are my 2 cents: just think "I'm not the target audience". And that's fine.

The difference between 2ms and 0.2ms might sound unneeded, or even silly to you. But somebody, somewhere, is doing stream processing of TB-sized JSON objects, and they will care. These news are for them.

For that you need a very centralized VCS, not a decentralized one. Perforce allows you to lock a file so everybody else cannot make edits to it. If they implemented more fine-grained locking within files, or added warnings to other users trying to check them out for edits, they'd be just where you want a VCS to be.

How, or better yet, why would Git warn you about a potential conflict beforehand, when the use case is that everyone has a local clone of the repo and might be driving it towards different directions? You are just supposed to pull commits from someone's local branch or push towards one, hence the wording. The fact that it makes sense to cooperate and work on the same direction, to avoid friction and pain, is just a natural accident that grows from the humans using it, but is not something ingrained in the design of the tool.

We're collectively just using Git for the silliest and simplest subset of its possibilities -a VCS with a central source of truth-, while bearing the burden of complexity that comes with a tool designed for distributed workloads.

It's fully caused by management mindset. There are companies that are investing hard on the AI trend, but the message is clear: all code pushed is your ultimate responsonsibility, and if it lacks quality or causes problems, you're on the hook for it; using AI hasn't changed that.

So if Spotify had a modicum of AI usage hygiene, plus accountability expectations for code quality, this would still mean a bad performance review for whoever introduced this issue (person or team; poor results and mistakes are never something that come from a single source)

Well, thanks. That small web just taught me in a very concise way a thing or two about bicicle braking technique!

I would enjoy this so much. Always keeping electronic parts around home, "just in case". It feels so profoundly satisfying when you finally get to put some switch or random piece to use for a repair, after having kept it stored for 13 years in a drawer (and through moving houses 3 times!)

As a Kodi user, I must say it is very good on its core, and very bad on the addons side (which arguably is the part for which it gets recommended mostly)

It forces its limited model of text-based folders-with-files to everything. Also it's all Python, and I don't know if it's me but I always find quality issues first in Python projects than anything else. Error control is usually very lacking, and it's so frequent to see error pop-ups showing on here and there. You enter a menu and the first entry selected is ".." which is to go back to the previous menu (poor UX). All in all, Kodi for me has always been a player with good tech (it all basically works, surround sound, codecs, integration with hardware, etc), exposed as very amateurish UI experiences.

Depends on the needs of the licensor. AGPLv3 solves the problem of other players taking the code, improving it privately, and not sharing those improvements. But AGPLv3 is not a silver bullet for people who write Open Source code and pretend to make a living from it. "Open Source is not a business plan".

https://news.ycombinator.com/item?id=45095581

I know the topic won't probably be about this -and I'll be reading the article next-, just wanted to share that this title perfectly reminded me the feeling of attempting the speed reading technique explained in this old gem of a video (minute 20:15)

BOOKSTORES: How to Read More Books in the Golden Age of Content

https://m.youtube.com/watch?v=lIW5jBrrsS0&t=1215s

Why does the Window Manager have to provide focus and even visibility info to the application? I could foresee an evolution of runtime controls where "Is Focused" is a user-selectable permission for apps, just like how the browser requires user approval to allow web notifications or PeerConnection access to network or webcams.

With default uBlock Origin filters on mobile Firefox, all Medium blogs show up as a blank page. Which in this day and age is akin to saying that the page is utterly broken.

Obviously no, if you trust that foundation; hence my

> few exceptions apply, e.g. the FSF in the past

Was I, really? Maybe, if you feel so... but I'd have to say that I had no idea.

What I'm suggesting is that a FOSS project without CLAs and a healthy variety of contributors does belong to the broad open source community that forms around it, while a FOSS project with such CLA is just open to a bait-and-switch scheme because the ownership stays in a single hand that can change course at a moments notice.

Whether the project stops receiving updates or not, is an orthogonal matter.

The only meaningful informed decision, but sadly much less known (and I think we should talk and insist more on it), is to be wary if you see a CLA. Not all do, but most perform Copyright Assignment, and that's detrimental to the long-term robustness of Open Source.

Having a FOSS license is NOT enough. Idealy the copyright should be distributed across all contributors. That's the only way to make overall consensus a required step before relicensing (except for reimplementation).

Pick FOSS projects without CLAs that perform Copyright Assignment to an untrusted entity (few exceptions apply, e.g. the FSF in the past)

Little known (apparently) thing from Spain is that our tips are not proportional. I see percentages everywhere when going out... 10% here, 15% there, so the quantities seem outrageous to me. In Spain if you want you leave a 1€ or 2€ coin, maybe 3 or 4€ plus some other smaller coins if you are more than 2 people. But that's it.

I've never seen a tip reaching 10€ in a restaurant, even in tables of 5+ people.

> For viva.com's engineering team, in case this reaches you: [...]

That's too kind of you, but on the other hand it really doesn't solve the issue of bad priorities and lack of overall Quality. Some engineer might log a couple hours fixing a Level 3 severity bug, emails will start working better, but the poor (or at the least, dubious) backwards technical stewardship (or lack of it) will keep going on inside the company, unnoticed from outside (until something bad eventually happens to some client)

Meh, already got enough in my plate. That "do it yourself if you need it" is technically correct for FOSS, but only when people need it, not the case here until it gets so popular that the whole organization decides to use it ;-)

If that's true, it sounds terrible, and a reason enough to not consider it at all. So much of the work in bug organizations is about just searching for past conversations when a similar issue had been discussed... Search must be flawless.

I gues the key here is where do you store that video!

Yours is truly an informed and well thought out decision! I appreciate it, and enjoyed reading your reasoning; thanks for the clarity and props for the whole effort of this project!

I agree that an extreme of the permisiveness is indeed the most likely to attract major usage. On the other hand, its freedom is more fragile. All is well with each project striking the preferred balance in that axis.