oxplot
I still have the pacman logs from the first package installed. It has traveled to three different machines, three filesystems (ext4, btrfs, xfs), two boot loaders (grub, efi) and two desktop envs (gnome2, mate+compiz).
I really can't imagine using anything else. AUR along with simplicity of the package source format and cleanliness of everything in general, makes this the perfect OS for a pragmalist like myself.
[1]: https://github.com/oxplot/raspberrypi-archlinux-installer
- Get a full on 80 hr/week job
- Swim in cold water
- Do HIIT - e.g. run like a lion is chasing you for a minute every day
- Watch horror films
- Drink coffee
- Have sex
On a different note, perfectionism can be a symptom of procrastination. It requires much less will power to fine tune an existing thing, than it is to start something new or work through early steps. If this is the case, then apply the usual anti-procrastination techniques: vow to put X minutes a day into a project in order to make it a habit and get the ball rolling; identify obstacles that are creating friction; re-think the design and simplify; breakdown the task to make it less intimidating; etc.
- iOS and Android both have screen time features to show you a banner when you've used an app for longer than a set time. This is a good soft block to start with.
- Auto logout after a set time. Having to login is one extra step that may deter you from accessing a website. This can be done with browser extensions.
- Auto delete apps after a set time (this is possible with MDMs). Again, having to install an app would be a big hurdle next time you want to sit back and scroll through clips.
- Throttle speed of a website - this one's a little brittle as you can quickly switch to a faster network, usually your mobile connection.
Then don't have it! Set things up such that only after someone pays, you get notified.
Perhaps your definition of hobby is different to mine, but hobby projects are exactly the kind you can abandon in a heartbeat. No long term customers, no guarantees, no obligations. In fact, we hear about countless HW and SW projects being abandoned left and right, right here on HN on regular basis.
> For that time cost, I want to work on a product that could go into production and pay for its own maintenance.
Hobby and high volume production aren't necessarily mutually exclusive.
I wanted to build a custom board to use USB-C power in my projects. Except the cost of a dozen boards assembled was quite high. So I made a thousand or so to subsidize the cost of development and production for myself. The chip I used went out stock (global chip shortage related) but until it did, my "hobby" project paid for itself and actually made me a small profit as well.
Whether it's a hobby project or a high volume production project, you don't want hundreds of hours of your time spent developing for it to go down the drain. In case of a hobby project, it probably means the one or two units you made are all that you're ever going to make. In case of a product you built in high volumes, it means a large gap in sales and lost revenue while you re-do the firmware for a new chip.
Just finished putting https://subzo.com.au up with pure Golang, vanilla jacascript and CSS. Works well with SEO, it’s fast, easy to debug and understand and doesn’t require me to touch node!
Gradual upgrade, as in you can update a single file to use the next major version. Not sure what you’re on about.
> hundreds of files which needlessly got changed
If you have hundreds of files and upgrading to a new major version all at once, you’re creating the exact risk that Go is trying to mitigate.
> this is redundant because the local go.mod file already has the semantic version of all dependencies tracked
The whole point of having full version path in each file is to allow gradual upgrade to a new major version/a completely different package. Listen to Russ Cox go over this many times.
> Users of packages aren’t alerted about new major versions
Fair point.
> For the client to update, it’s not a simple path change in go.mod
It's a simple command:
gofmt -w -r '"github.com/logrusorgru/aurora" -> "github.com/logrusorgru/aurora/v3"' ./
> Maintainers should be able to increment the major version via Git tags.
Go is not tied to git or any other single SCM system. They can however be pragmatic about this.
> I get why these rules exist, and I think they are great for large open projects
You either don't, or you think that smaller/trivial project's requirements somehow take priority over larger ones. There are plenty of toy/application specific/scripting programming languages built to be used to write a few hundred lines or glue things together. Go specifically and repeatedly states that it's aimed at large, distributed and long term projects with lots of changes over time and many contributors. You know that going in. So you're criticizing (poorly I might add) the very notions that this language is built upon! This is like criticizing an industrial kitchen equipment for not having pretty colors and curvy shapes to match your home decor.
Large camping fridges are as close as I have seen, but I'm sure someone's thought of one for domestic use.
As for practicality in the kitchen, I can imagine a design where you have multiple medium sized fridge drawers. Once pulled out, you can open their top lid and access the content. This way, you don't have one deep container, but rather, multiple shallower containers. For efficiency, a single compressor can feed all of them.
EDIT: actually I've seen freezer drawers - you just need to dial the cooling down a bit.
Another idea: Vertically long rectangular compartments that can be pulled out individually. Essentially a whole bunch of vertical drawers of different sizes, with meshed walls to allow air to pass through them.
Another silly idea: a horizontally mounted ferris wheel
There is a big difference between feeling suffocated in your own home where no one else is involved vs. among people you could potentially be putting at risk.
I never do because I feel suffocated.
> see a doctor
Thanks for the unsolicited advice. I in fact have and have been told not to wear clothing that makes me feel suffocated.
> the burden of wearing a sweater is just incredible in some of these comments
Your lack of sympathy is equally incredible
Travel Tips
It really depends on what corner of Twitter you live in. I follow a dozen or so people and see nothing but high quality content.
Clever people value their time. When twitter reaches a large audience and has the lowest friction for sharing content, then that's what they use.
- Twitter hosts some of the highest quality content that get into the nitty gritty of some topic, exactly because it's so low friction to post to Twitter. Those of you saying "just put it on a blog" are either oblivious to how much more effort that is, or have already spent a lot of time making blogging low friction for your needs. That's not the rule however.
- There are countless posts with a mixed quality here from NY Times and other subscription based sites that show a pay wall when opened. Do you propose banning those too?
- If someone really cares to find out what's there to see, they'll sign up. If not, they move on and the post doesn't get any upvotes. Works itself out. As others have mentioned, script it out of your view if it really bothers you that much.