HN user

Shywim

162 karma

[ my public key: https://keybase.io/shywim; my proof: https://keybase.io/shywim/sigs/KaZtmMlxnaTcVlDsxNK-rRAm9Y7mBKVGgF1OZEtPx0o ]

Posts5
Comments45
View on HN

Note that carto.tchoo does not provide real position in real-time: it only has access to departures, stops, delays and suppressions and interpolate position based on this.

This means that if your train is running at half-speed or stopped but does not result in an official delay, the position will not match reality.

The statement that current AI are "juniors" that need to be checked and managed still holds true. It is a tool based on probabilities.

If you are fine with giving every keys and write accesses to your junior because you think they will probability do the correct thing and make no mistake, then it's on you.

Like with juniors, you can vent on online forums, but ultimately you removed all the fool's guard you got and what they did has been done.

Sizing chaos 5 months ago

Body shape is not only about obesity, or fat, and I think it's obvious the author don't talk about this when speaking of body shape.

So, it's been one year since I use Zed daily, and I didn't encounter this issue, or any other issue for instance, everything is smooth and I never encountered a failure or a crash.

I work on large (everything is relative, though) monorepos, that would probably qualify for this limit, and I remember already did the kind of "workaround" discussed in this issue years ago on this device. I think it's hard to blame the software when the default file limit is so low depending on the languages you work with.

Anyway, if you would encounter this problem, you would have already encountered it with other tools, or else this is fine.

Not for me, MacOS 15.4:

    $ ping hello.localhost
    ping: cannot resolve hello.localhost: Unknown host

It says "values of type B", as in "instance of type B", can be passed as if they are "instance of type A" (which they are actually).

But yes, values inside B specific to type B will not be able to be accessed when manipulating the type A.

The logical conclusion from statistics is hybrid work. I am full remote because of the distance, bust most of my company is hybrid, and my experience is exactly as described by the results of the Microsoft studies.

I go on site 3-5 days per month, and I always connect more (more than 0) with people outside my team and happens, even on work related topics which enable new interesting findings and what not.

It helps that the company where I work has a culture that make people want to go to the offices even if they are not required to do so. There are pics days when the office is full because people want to see each others, then they are free to remote work any time it is wanted/needed.

I think that works out if you are alone, if you are with other people, the waiter will probably interrupt the socialization you are doing with the people you are with, causing stress even for the waiter.

Also we should recognize that the waiter is often looked down at, it is not a very nice job, and as a human being, having a poor experience with some customers will probably pass on to other customers, etc...

I'd go as far as having a job with "wait" in the name, and having to wait, calmy and happily or else you don't get your tip, is not so far from slavery.

Most Git GUIs map fairly closely to the underlying git model.

Maybe, but most Git GUIs don't provide clear error messages. This is the case of VSCode, which my teamates keep using. When you use Git CLI you can just have the original error message and know what's wrong.

I was also burned by sourcetree some years ago where it lost part of my code while doing a merge I didn't even understand.

I am not a Git expert. But I can remember the 5 commands needed to do my job every day: `commit`, `push`, `pull`, `rebase`, `checkout`. (you can also add `add` and `status` to the list if you want)

They're straighforward, except for `checkout` which is adressed by `switch` for the main usage.

If you use it wrong, Git CLI will tell you in most of the cases, and even tell you how to do what you intented to do. Git GUIs will probably tell you something wrong happened and left you at that or try to be more intelligent than you are and do something wrong.

Isn't that just being incredibly lazy.

-> this is what I'd answer to do those Git GUIs.

Isn't that just being incredibly lazy.

-> this is what I'd say to people who won't write these 5 commands on a sticky note or something and keep it for a month before realizing it wasn't hard to remember once you _commit_ to it and that Git is not hard, minus exceptional problems but Git GUIs absolutely won't help you with these exceptional problems.

The same confusion exists between Visual Studio and Visual Studio Code.

Also, Eclipse Theia could be the name of the last version of the Eclipse Java IDE since they named every major release of their IDE until recently.

Maybe they should have gone with Theia by Eclipse, or just drop the Eclipse in the name altogether.

In short: X.org is a decade old display server that became the standard to display graphical window on the majority of Linux distribution. GNOME, KDE, XFCE and others are/were client to this display server.

Wayland is a new protocol where the window manager (ie GNOME, KDE,...) is responsible of directly managing the display. Each window manager must reimplement this protocol (or use a library already doing this work) which enable them to have more control over the windows.

Applications must also directly support Wayland like they did for X.org before (which was the default commonly used, so no problem) or the user just have XWayland installed on their computer to show X.org windows inside a Wayland WM but then the application may not display correctly (blur, artifcats,...)

Some replies say that the user should take a second look at what permissions they give, but in the case of Android apps the permission to use the Account Manager (used to register a service account like Facebook, Google, Twitter or any other things that need to synchronize in the background) is displayed as a "Contacts" permission to the user.

So some apps like Facebook might synchronize or make other uses of contacts with their service accounts, but many other service don't do anything with contacts and doesn't EVEN request the actual contacts permission but their permission request is still displayed as "Contacts".

How can the user be able to do responsible choices in giving apps permissions when the permissions layer of the OS make no sense?

You can't but you can host them on your own and then put a link to them which is more cumbersome both for the writer and the reader who has to click a different link for each svg (or other asset) instead of just clicking one link to an article which inline them.

IMO the web was made for discovery. I don't see why would people would want to consume what I write on Twitter or Facebook where there is no formatting available (or worse splitted in small messages on Twitter). If these people prefer to stay in their walled gardens, good for them, but I don't want to strip what I write to please them. Why won't a link on these platforms suffice since they have their "cards"?

Also if people want syndication in one place, there's still RSS aggregators which is a technology that works even if everyone like to pretend it doesn't.

I like competition, but regarding "Google-less Android alternative" why everyone want to do his own project when this is a niche market with few developers who want to use their time to do this, and even less in the long run?

Why do people don't join their effort to put up something better, faster, safer?

React 16 9 years ago

Depends what you call idiomatic. I dont think JSX is really a JavaScript idiom, more like a HTML idiom applied to JavaScript which happen to be often used together.*

At the end of the day, I think that calling something idiomatic is subjective and so, varies from people to people.

*: to be clear, my point is many people use JSX with React because it feels idiomatic (I manipulate HTML/DOM, so why not just write with HTML-like syntax?) but it is not idiomatic to JavaScript and I don't think the other React APIs are that nice to use. If I didn't use JSX with React, I'd tend to use other framework because, in my opinion, they make more sense.