Heliosmaster

Disk Inventory X for MacOS: http://www.derlien.com/

I believe so too, but that does not mean anything for my argument. They are trying to rally people so that they can get better profits. The fact that maybe (and i'm skeptical about it) other people do too, it's coincidental for them, i'm sure.

many developers have really no choice (at least not individually). They don't really have the means to vote with their wallets, as foregoing the whole iOS market is.. not a choice.

What EPIC is doing is trying to rally people on their side of the fight.

This is the same reason why people (workers) have unions, in the traditional job market. It's not really comparable because developers are not workers, but there are some similarities: Apple benefits from the developers (immensely, with your Windows Phone example) and the developers too.. but Apple has the upper hand, by FAR.

The fact that you used the word globohomo is already telling enough: https://www.urbandictionary.com/define.php?term=Globohomo

There is also https://github.com/borkdude/babashka which uses Clojure to create scripts

Any recommended resources to get started with SDR?

We are building Nextjournal[0] exactly for this purpose.

It's a platform for interactive notebooks built on immutable and persistent storage (Datomic) and Docker:

- Changes to the document are automatically versioned to an immutable database (Datomic). Previous versions can be accessed and restored any time.

- Uploaded data or generated result files are automatically versioned in append-only content-addressed storage and can’t be accidentally overwritten.

- Changes to the file system state can be committed as Docker images. Reproducibility is ensured by referencing these images only by their immutable hashes.

[0]https://nextjournal.com

There is the problem that everything can be subdivided in a bunch of menial task so every cog in the system isn't aware of their impact. It already happens a lot in software.

the idea of Hippocratic Oath reminds me of Asimov's Three Laws of Robotics in "The Naked sun" (SPOILERS ahead): the detective realises that the normally quoted First Law of Robotics ("A robot may not injure a human being or, through inaction, allow a human being to come to harm.") is actually just an approximation, he argues that the real Law is "A robot may do nothing that, TO ITS KNOWLEDGE, will harm a human being; nor, through inaction, KNOWINGLY allow a human being to come to harm."

This is important because even though robots really try their best, different robots could perform sub-tasks that look very harmless by themselves, but combined kill a human being:

- A robot is instructed to pour this bottle of poison into a caraffe of water and then leave the room

- Another robot is instructed to enter the room, take the caraffe of water and give it to a human to drink

The human is poisoned, but none of the robots are directly responsible (in the first law sense). Is the act of connecting the two dots the evil deed.

FWIW Clojurescript can also be used in ESP32: https://blog.tindie.com/2020/07/clojurescript-on-esp32-why-n...

Mike Fikes and the team at Vouch.io are doing some interesting work there, using cljs for IOT.

(italian here) completely agree. It's not very easy to find a coffee shop where the espresso doesn't taste burnt. I have the feeling the baristas have good technique, but the machines don't get cleaned / serviced enough.

Or maybe it's just me, trying more and more different coffee places around europe.

A bit of a plug, but this is exactly the reason why we are building Nextjournal [0].

We've built the platform from the ground up with immutability in mind, leveraging Clojure and Datomic which are a great fit for this architecture.

[0]: https://nextjournal.com

This is the main reason why we are building Nextjournal [0]. By using immutability of Datomic + Clojure the code (and the results) are immutable and permanent.

[0] https://nextjournal.com

Anecdotally, I've always found really up-to-date information. Worst thing was that some rural areas had not a lot of data (so I added it, at least a bit).

OSM is a dataset. That's free and open. There are different tile servers (https://wiki.openstreetmap.org/wiki/Tile_servers) but they each have a different policy (https://operations.osmfoundation.org/policies/tiles/)

In a nutshell: you can't just use them in production for your app. Development shouldn't be a problem.

What you're talking about is precisely the commercial service that Mapbox offers. OSM (+ some extra stuff).

Alternatively, you're free to spin up your own tile server. That way you don't pay anyone else (but you pay your server).

I use Mac and emacs keybinding all the time. C-a, C-e, C-k, C-y.. not sure what you mean.

Org mode in emacs seems to fit your description pretty well (for Emacs users, at least)

Also i think it's a great use case for the data-drivenness of clojure :)

From the article, it seems like the contract was ending, and there were talks of a 6mo extension when everything came apart.

FWIW Brave does that. If you reach a page with a 404 a banner will appear on top with a button to try and navigate to the latest version of the page you're looking for at the archive.

Which monitor?

Not really. It depends a lot on the habit. Plenty of people in Italy take the car to drive less than a km to go a shop, and then come back, especially in mid-to-small cities

Not really. I can't contract you to do something illegal for me (e.g. kill somebody, even me!). Now, if you are saying that these kind of contracts SHOULD be valid, that's another thing but that's not the case at the moment (and rightly so, imo)

I guess it was done on purpose, but essentially it reminds me of the syntax for graphviz: https://graphviz.org/

I'm fulltime Clojure since 2014, and I can't say enough how happy I am. I find a lot of joy, every day, in my work as working with a LISP really fits with how my brain think.

The community is great and the language leaks through the people: you'll often find very pragmatic (even conservative) approaches.

If you are looking for some more testimonials, look no further than Uncle Bob [0] and Gene Kim [1], but there's several more results online.

Lately, I tried to "modernize" a little bit the Clojure course that I used, many years ago, to start, and you can find it at [2]:

- [0]: https://blog.cleancoder.com/uncle-bob/2019/08/22/WhyClojure....

- [1]: https://itrevolution.com/love-letter-to-clojure-part-1/

- [2]: https://heliosmaster.github.io/academy/

Yes. I can say that doing concurrency in Clojure is particularly easy, check for yourself: https://www.braveclojure.com/core-async/

There's a typo, it's https://www.flattenthecurve.com/

Precisely. There's a lot of (domain) data manipulation before it gets to the DOM, and that's where cross-platform clojure (CLJC) excels.

To be honest, I've done Clojure full-time (and exclusively) for 6 years now. I've almost never had to use Java interop. (With CLJS I did a little more JS interop).

There were always wrappers written by somebody else that always did what I was looking for.

You should check Michiel Borkent's work (borkdude):

- Babashka: https://github.com/borkdude/babashka

- Clj-kondo: https://github.com/borkdude/clj-kondo

- Sci: https://github.com/borkdude/sci

- Jet: https://github.com/borkdude/jet

But again, those are tools (especially babashka) from a Clojurist's perspective

From the comments here, I think many people are missing a very important factor: while we (as technologists) focus on what WE think of the iPad, or what we can do with it to be productive, this is only part of the picture of the general population.

In my opinion the iPad has had a tremendous impact within the general population and (combined with smartphones) got rid of the PC altogether for the average family. And tablets, especially for the elderly, are a true game-changer.

My mother, not a technologist at all (she doesn't even have a cellphone) cannot live without her iPad. Granted that she could do everything with a smartphone, but the bigger screen of an iPad is particularly good for people who have a waning eyesight and, in general, might require a bit of a bigger UI (bigger buttons, etc.).