1,241 karma · joined August 14, 2013
I've always liked the idea of moving general compute to the database, but usually in an organisation the databases are pretty tightly locked away and it becomes a pain to get the right versions of your libraries installed.
Want to run an algorithm on 10 nodes for 5 hours? No problem. Want to leave something running for days connecting to the twitter firehose? Sure.
However building PCs and your own clusters is quite fun! Check out these https://www.picocluster.com/collections/cubes/products/pico-...
When I went to Germany I was amazed at how bad their toilets were and I often had to pay to use them.
I think the "quiet pc issue" is a solved problem provided you aren't building a massive gaming machine.
I've just updated my blog and would appreciate any feedback https://trengrj.net/
Evil is a strong word but imagine a future where ISPs chop and charge your for your data like cable and try to keep you looking at "their" content.
Additionally I've recently started using elasticsearch docker containers and I found Linux is a far better host than Docker for Mac (as it still runs a tiny Linux vm with associated slower disk access).
It is hard to argue against free Netflix etc but the end goal of these activities is clearly to centralise the internet (targeting poorer / disadvantaged people first), and turn the internet into a modern television-like propaganda machine.
I really enjoy using sqlite. Not everything needs a client server model, and having your entire database located in a single file makes a lot of things way easier.
For Microsoft to become a true open-source company they would need to open source Windows, which goes against their advertising, telemetry, and tracking goals.
Pros:
* The type system
* Being able to mix functional and OO design coherently
* Less verbose than Java
* Utilise existing Java libraries
Cons: * Huge amount of syntax to learn
* Fragile and slow package managers
* sbt uses Ivy and so downloads package files in a single thread. In Australia this is horrible
* too slow for scripting due to JVM boot timeI don't like its effective ownership by redhat and its monolithic nature however this can be solved in the long run by forks and standardisation.