reddit_clone

Yep. Containers are great. But haven't seen anyone else using it near me though.

One feature I was missing from Chrome was Tab Groups. But recently (I don't know when it started) the feature showed up in FireFox too :-)

Yep. I arrived at the same solution after trial and error.

Org-mode is the most appropriate answer. It is as simple or as sophisticated as we want it to be.

Obviously one needs to be an Emacs user first

I have always felt 'Let it crash' is an unfortunate turn of phrase that gets a lot of negative attention.

A 'crash' in most other language/ecosystem means likely a catastrophic failure of the application, ending in a core dump.

Erlang's error handling is way more nuanced than that blunt phrase indicates.

Yep. I do as much real work as possible in Emacs. Magit/Org-Mode/Org-roam/Org-gtd/Babel are all pretty essential to my workflow.

My experience aligns with this. I work for a bigco. Yet to meet a fellow Emacs user.

Also you can see much farther between cars. I usually ride switching left of the lane to right of the lane occasionally, to create lateral movement so car drivers will notice more (one hopes).

I am really interested in Sous Vide cooking. But cooking meat in plastic bags turns me off.

Went through the whole article. Tried out some commands.

I haven't 'got' it yet. I am sure I will after some regular use.

But being a long time Magit user, its hard to move to anything else.

Hmm. Here I thought it was about a special martial art variant for chair bound developers !

Sad thing is Perl6/Raku is a nice kitchen-sync language with some pretty sophisticated constructs!

Unfortunately it has no mind-share.

Low effort Youtube shorts with AI voice annoy the crap out of me.

After all this hype, they still can't do text to speech properly. Pause at the wrong part of the sentence all the time.

From what I had read in passing and remember.

  - They were loud (sonic booms were nasty).

  - They were expensive to maintain and operate. Guzzlers. (Britain and France clung to them as a matter of pride/ego)

  - They were narrow and uncomfortable. I have seen videos where there is space only for one stewardess to walk. I had been inside of one in Seattle museum. Very cramped.

  - As you mentioned, ticket cost was high.

  - I suspect people traveled in these mostly for bragging rights.

This sounds very nice!

We also have Microsoft authentication that displays a number on the browser and asks you to enter in on the device! :-(

>Forsyth was a staunch supporter of Brexit, becoming a patron of Brexit campaign group Better Off Out, and wrote of his scepticism of climate change in his Daily Express column.

Nobody is perfect :-(

> fairly easy

Very subjective. I understand the rite-of-passage impulse to build one's own config. But it is simply too much time/effort investment if you are relatively new. This I say as someone who had my own config for a couple of decades.

When I came across Doom, I threw mine away and just adopted it. I even learned to like VIM/VI style text editing to use Doom effectively.

I also like the GodMode/Leader/Model style of text editing. The keybindings are more intuitive and more discoverable. When I enter a key and wait a bit, doom pops up next available options. I no longer memorize the keybindings. Just use the whichkey integration to find things I use infrequently.

Not to mention that it is well tested with the sets of packages for each release.

Obviously, not for everyone.

But I am a happy user and hope it exists for a long while.

APL is the densest language I have come across.

There may not be enough code out there for LLMs to pick it up though.

There is no hard and fast rule (for me).

It is easy to start creating objects in the repl (say if you are testing an API) and work with those created objects in the repl, one step at a time. You are able to observe the behaviour of the objects every step of the way. This gives you a much better idea when you are writing the functions (usually copy-pasting from repl) in the editor.

I am sure it can be done from the editor itself. (say using the 'comment' block in clojure). It is just matter of preference.

I have seen attempts at actor systems like erlang/beam's. Scala/Akka seems to have been a success?

Share nothing, green-thread/coroutines also seem popular now a days.

I get very annoyed at the AI voice overs in youtube shorts and videos (which are showing up more and more lately).

I just close the tab when I realize it is AI. Not sure how long I can do this.

>Maintaining a complex Emacs config is a chore. I have given up and adopted Doom Emacs. Let cleverer people do the wrangling

Exactly. I start in the repl, but when it becomes a few expressions deep, I transfer it to the editor and turn it into a proper defun. Start 'sending' the defun to the repl and test it out in repl. Rince repeat.

>litestep

Brings back memories !

As a wannabe home lab hacker, but never had the energy or knowhow to get started, this thread is a goldmine of information!

Exactly my setup including the #tag's. It is my second brain.

What I love about this is the fzf's fuzzy narrow down. You don't have to start at the beginning of command, you don't have to worry about exact spelling. Just a few snippets you remember, it will narrow it down really fast.

I use the same fuzzy search narrow downs in Emacs.

I miss it everywhere else.

On a related note, I would love to see an animated explanation for how sail ships worked.

As a fan of Hornblower series,I suspect most of the relevant details went over my head because I didn't understand this.

I find python is not a natural fit for shell script replacement (may be I am doing it wrong).

Executing a process and bringing back status, stdout and stderr seem tedious. While in Perl, it is as natural as it is in a bash script (well almost).

Raku on the other hand is _Fun_.

Indeed Raku is a delight to use for 'shell scripting'.

Perl was originally written as an amalgamation of grep,sed,tr, awk and I am sure a few more unix utilities with their own mini languages. The idea was to use one language instead of tying together half a dozen mini-languages in a shell script. And it worked really well. Perl being a demon with text munging didn't hurt.

Raku keeps this heritage but adds so much more (for better or worse :-) ). It inherits ideas from Lisp and functional programming languages. The thing that impressed me was, how easy it was to use concurrency.

You probably heard this one before. After a while the parens do disappear. When conventionally indented, lisp users see only the indentation and not the parens.

With structural editing, no one ever have to match parens or count parens at the end...

YMMV ofcourse.