Omakub – A Developer Setup for Ubuntu
omakub.org
omakub.org
Also not a fan of introducing new Linux users to wget | bash ...
This solves the discovery problem of knowing what's out there and what's possible. Personally the discovery problem is why I like full featured IDEs: GUIs do a better job of presenting possibilities and they push features to you by default needing to manage them.
This is no difference than windows or macOS having the usual defaults.
I like the styles it comes with, the terminal, and the way the workspaces and shortcuts are set up.
Standard Gnome shortcuts for workspace switching (Win+F1) and dash application activation (Win+1) are replaced for no particular reason, and the new Alt+number mappings likely conflict with mappings in several applications. At least Emacs.
n00b ricers…
No, won't execute scripts from people which know basically nothing about security...
The usual argument against curl|bash scripts is that they don't respect program boundaries, may do unknown system configuration that would affect other programs, and could be impossible to remove.
And "initial system setup" scripts like this one do all those things _on purpose_.
I'm curious about the choices of Alacritty over Wezterm and Zellij over tmux though. Especially if going with zellij then why not use wezterm as well? Anyone know?
I'm sure many of these exist but DHH seems to have put a lot of thought and attention into his and it's worth checking out.
I've been following along on Twitter as he documented his transition from OSX / Textmate to Ubuntu / neovim. Fun to see.
Thanks for sharing
I feel personally attacked. I have a memory of a fish and would hope if I really could remember the thousand shortcut I need to move to rely solely on keyboard.
This is similar to an Ubuntu "spin" so I'm ot sure why someone would go through all the effort but of customization with out releasing a proper remix that just gives you the out of box XP with lower friction.
This clearly isn't meant for containers, maybe folks who dev on windows and use a VM will find it more useful given WSL2
For disambiguation, this project is also not implying the following:
Om - this is not a flavour of Linux oriented to Meditation.
Maku - this project is not associated with the city in Iran.
Oma - this project was not created by a German grandmother. DHH is a man from Denmark.
You don't prove a point by being silly about random tokens out of context.
"kub" in the context of tech, specifically tooling for a developer of web tech, it's better to avoid using names that have similarities to tools they don't touch.
It's good marketing because it's good UX.
You can continue your pedantry if you like, the context of our tooling is what it is, and no sort of absurd reductionist argument is going to change that.
Very cool, I'm both impressed and inspired!
In fact the scripts for Linux and macOS are almost identical.
Honestly a few app being installed barely does any damage to me. What's your concern?
Like every other Linux user, DHH has an opinion on how to set up his OS
Most webdev tools are written in JS (or at least used to be). Web browsers run JS just fine. Webdevs, then, should be striving to make sure that their JS-based tooling actually runs in the browser—instead of targeting the non-standard, ever-shifting, and unreliable APIs of NodeJS et al.
There's not an especially good reason that you shouldn't be able to build 80% of the projects on GitHub that belong to this milieu by simply:
1. downloading a copy of the source code
2. opening README.html
3. following the instructions in the workspace on the resulting page that says "to build this project, drag and drop the project folder here"
NPM/NodeJS programmers so desperately wanted to be taken seriously that they reimplemented wholesale all of the bad, fiddly things about toolchain installation, configuration, and maintenance that afflicts all other platforms/stacks that didn't have the it-just-sort-of-works-for-everyone strength that browsers have (and is largely the reason why so many webdevs choose to target browsers in order to reach end users in the first place). The perverse irony of this might be amusing if it didn't result in so many pointless excursions and wasted hours of human potential spent nursing the unfortunate status quo associated with `npm install`, yarn, etc.
> 2. opening README.html
> 3. following the instructions in the workspace on the resulting page that says "to build this project, drag and drop the project folder here"
i don't want to do all this stuff. literally none