HN Simulatornew | past | comments | lists | submit | monkaiju's commentslogin

Good! Self driving cars are a ridiculous, but potentially lucrative, distraction from what we should be investing in (trains, buses, light rail, etc)

decentralization is good actually.

there's a predictable natural disaster heading to where you live (hurricane, typoon, meteor), are you getting on light rail to escape?


How predictable? Emergency shuttle services could be a thing.

Unless you like the panic and chaos where all the individual cars create traffic jams.


could be, but won't be. where do we store all the idling emergency shuttles during non-emergency times?

Your don't store then, you use them daily. Many new EU trains are double function.

Micro$lop strikes again

Hard disagree, for the vast majority of Dev work this is not the case.


You don't use cloud AI for the vast majority of dev work?


no, I dont use it at all lol


Pretty funny tbh, it is amazing these clowns have so much influence over such large investments...


We already have a no-LLM policy where I work, and we're moving faster and delivering bigger features than ever.


Bold of you to assume we have any say...


Yet we did, indirectly.


Indirectly is doing a lot of work there. The US is an extremely disenfranchised place, and the choices are both pro-capital and will never actually represent the people in any meaningful sense. This liberal individualism framing only serves to bolster nationalism and divide groups when what we really need to be doing is recognizing our shared goals, with "we" being the international "we", and figure out who our enemies really are.


Hopefully riseup can pick up some of the slack here, but more decentralized services are needed.


Are there interesting approaches to the problem? Tor comes to mind but that's not really accessible for readers


I mean, if they relinquish their ownership of the plane and joined in with some sort of council that determined how to manage such assets I bet everyone claiming to be an anarchist would be fine with it. Anarchy as a political ideology doesn't mean no rules, it means no rulers.


Maybe for big companies that irresponsibly vendor-locked themselves, but I work at a SMB (~60 employees) and we switched to Forgejo in a couple days


I would not call it irresponsible. If you have a big, long running project you're going to want to develop complex pipelines and build processes to help with development and testing. This will save a lot of time and create a more consistent workflow, but switching vendors can require redoing work that was built over years.


> you're going to want to develop complex pipelines and build processes to help with development and testing

Opinion: Complex build processes are great. Complex _pipelines_ are a trap. I'm in a position to see the output of a lot of teams at a very large company. The teams that have complex build processes _that they can run locally_, and then have some trivial CI yaml to run the build, are doing great.

The teams that designed their build around CI are brittle and eventually end up in a state where they can _only_ do some parts of their build on CI.

IME it's worth it to set very hard boundaries shaped like: (1) Everything needs to be able to be run locally (usually in a devcontainer), (2) CI config shall be stupid simple. If you have more than like two lines in a script section, it goes into a Tools/Build script file that must work locally and is just called in a one-line CI script.

#1 guarantees you can operate without CI, and #2 guarantees you can move CI providers trivially.


>develop complex pipelines and build processes to help with development and testing. This will save a lot of time and create a more consistent workflow,

Beware the trap of making the pipeline so complicated it's like code except you can't debug or unit test like regular code, and it takes an hour between attempts to see if a change worked.


GitHub encourages this by using an arcane pipeline configuration format that could have been a shell script and has no way to run it outside GitHub.


If only we had a way to run code in a pre-defined isolated environment that can hide most of the differences of the actual hardware...

Oh, we do have Docker/Podman?

Then why not use _them_ to define your build pipelines? Bonus points: you can run them locally without tearing out your hair. And you can use normal scripting languages and task runners (taskfiles, good old makefiles, Ninja, etc.) for sequencing.


Happier everyday to completely avoid this cognitohazard. I'm lucky to be on a team with a no-LLM policy too!

Despite that, some other parts of the business are trying their hands at playing slop slots...


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: