- dented42 parentIt looks like there’s a download link that contains the source code. Presumably you untar it, follow any necessary build instructions, and then run it.
- This very much depends on your definition of ‘best’. While your criticisms of the environment are valid, smalltalk is flexible in tangible ways that Java couldn’t match. Java took the OO model of smalltalk and make a bunch compromises that had big negative impacts on the language that are still there today.
Smalltalk was (and still is in some places) successful because of its portability, flexibility, etc. while it hasn’t enjoyed the degree of success as Java, ruby, perl, python, C++, and friends it would be a mistake to call it just a you.
- I can’t be alone in this, but this seems like a supremely terrible idea. I reject whole heartedly the idea that any sizeable portion of one’s code base should specifically /not/ be human interpretable as a design choice.
There’s a chance this is a joke, but even if it is I don’t wanna give the AI tech bros more terrible ideas, they have enough. ;)
- This is blatant misinformation. Firstly this has nothing to do with the patriot act, I’m pretty sure the patriot act expired years ago.
But more importantly it doesn’t seem like the government is trying to ban anything, they’re just extending the anti-fraud / anti-money laundering measures enjoyed by the ‘traditional’ financial institutions to the world of cryptocurrency.
Those measures don’t prevent people from doing ‘suspicious’ things, they just treat certain transaction types with more care because of the increased likelihood that they are evidence of a crime.
- This is my thought exactly. I really love the idea of open hardware, but I don’t see how it would protect against cover surveillance. What’s stopping a company/government/etc from adding surveillance to an open design? How would you determine that the hardware being used is identical to the open hardware design? You still ultimately have to trust that the organisations involved in manufacturing/assembling/installing/operating the hardware in question hasn’t done something nefarious. And that brings us back to square one.
- This is very sensible but I think is missing one key insight. Very often side projects are ridiculous things that serve very little actual utility but we build them because we think it’s cool. If, for example, I want to writing a reminders app for my groceries that uses a cluster of 8 machines because it’s silly and I want it, that’s what I’m gonna do.
But if you’re building your side project just to serve a purpose and you’re trying to be as efficient as possible then yes, absolutely this advice is incredibly important.
- I genuinely don’t understand why that matters. The fact that there exists bad editors that don’t support my workflow shouldn’t prevent me from using the tools that I like and am comfortable with. I use editors that don’t screw up makefiles so what’s the problem? If I take your argument to the absolutely absurd logical extreme, I shouldn’t use lower case letters because some character encodings don’t support them.