- Completely normal yes. Repos are cattle not pets.
- I hear a lot of people already roleplay with LLMs which is pretty much that.
- > It’s not just to save the effort— stories are good because they surprise, challenge, and inspire us.
Maybe, but that's the minority of demand. Most book sales are to people looking for something comfortable - think the near-infinite supply of practically interchangeable romance novels or detective stories.
- There are only so many short names to go around.
- A friend created a library called library which was kind of a converse to that (you had to link it with -lrary). It was funny for 30 seconds and then just annoying.
- Yeah. Being able to write code that's polymorphic between server and client is great, but it needs to be explicit and checked rather than invisible and magic. I see an analogy with e.g. code that can operate on many different types: it's a great feature, but really you want a generics feature where you can control which types which pieces of code operate on, not a completely untyped language.
- Not my experience. For example the "official" way of achieving the equivalent of sum types (the visitor pattern) is so verbose that idiomatic Java tends to use the equivalent of a "single table inheritance" style instead of proper domain modelling, which inevitably leads to all sorts of logic errors. Idiomatic Java uses "magic" AOP because the alternatives are too verbose, but this also inevitably causes logic errors (indeed in some ways it's worse than C where you'd do the equivalent thing with a preprocessor macro, which is at least a bit more visible in the code even if only due to conventions like UPPERCASE names). What kind of logic errors are seen in C that you would claim that idiomatic Java avoids?
- I think allowing the definition of open source to be muddled would be a big mistake, especially now that some entities are trying to whittle away users' rights while continuing to benefit from the positive vibes of open source. The OSDI/DFSG/FSF definition is a clear, simple line in the sand that has served the movement very well; there's no reason to change it. Yes some entities actively participate in their community and others do the bare minimum, but it's always going to be possible to be more or less communitarian.
- As I said on https://www.hackerneue.com/item?id=46214609 , that statistic doesn't mean what you think it does. The article I linked doesn't have figures for Tokyo but it has Shanghai which is comparable; there are around 4x as many jobs within 30 minutes by transit in Shanghai as by car in LA, while the population is only 1.5x bigger.
- Yes, that's what a tragedy of the commons looks like. An individual in a given city will have a shorter commute by car. But the more people who are using cars, the worse everyone's commute gets.
- > You do realize that they get frozen only because of the fiat system regulations/laws?
Well, sometimes. Sometimes they get frozen because the exchange operator decides to take the money and run.
- > So, written in C/C++?
Not in the sense that people who are advocating writing new code in C/C++ generally mean. If someone is advocating following the same development process as Chrome does, then that's a defensible position. But if someone is advocating developing in C/C++ without any feature restrictions or additional tooling and arguing "it's fine because Chrome uses C/C++", no, it isn't.
- Any evidence for that impact? While the prospect of displaced traffic was very much hyped, the data I've seen is that there's very little of it.
- What does the size of the state have to do with anything?
- Neither of which is required to use the road in all cases.
- It's a tragedy of the commons. For an individual, private car is faster, but the resulting traffic ultimately makes things slower for everyone. Public transit in Tokyo is faster than private cars in car-oriented cities.
- > Average commute in Tokyo is 45 minutes to an hour one way: https://nbakki.hatenablog.com/entry/2014/08/05/231455. Average commute time in Dallas is 26 minutes one way: https://dallas.culturemap.com/news/city-life/dallas-suburb-s...
People in Tokyo will accept a longer commute for the sake of a better job or housing or both, because the commute is less miserable (and also because employers pay commute costs).
> I’m not aware of any transit-oriented city where average commute times are as low in absolute terms as in sprawling, car-dependent American cities.
Transit-oriented cities provide access to more jobs within a fixed range like 30 minutes even for car commuters. https://www.nature.com/articles/s42949-021-00020-2/figures/4 . People in Dallas having shorter commutes isn't a sign that Dallas is built better, it's a sign that people in Dallas are avoiding switching to otherwise better jobs because it would make their commutes worse.
- The MTA does not overpay when you compare to other employers in central NYC. It's an extremely expensive city due to housing policy failures.
As for commercialising the stations, does the MTA try to do so and fail, or are they forbidden from doing so effectively (often by the same people who are pushing the narrative that there is something wrong with the organisation)?
- Almost all rail in Japan is subsidized, directly and indirectly. Yes the single line that is the Tokaido Shinkansen is immensely profitable; even then, JR Central does not pay market-rate interest on even the portion of the construction debt that was not absorbed by the government.
Sure, but even though it's "build time" it feels more like runtime (indeed I think the only reason it works that way is your code is being run at build time). I should be able to look at a given piece of code and know locally whether it's client-side, server-side, or polymorphic, rather than having to trace through all its transitive imports.