willjp

I'd be much happier if UBI proposals were higher. Living on ~900$/month nowadays would be difficult.

20 years ago I was able to split rent for a tiny concrete windowless-basement-bedroom for 450$/mo, trimmed my grocery/cleaning bill down to 100$/mo by eating nothing but rice, beans, and frozen vegetables, 120$/mo for a phone and internet (which I consider essential), and another ~80$/mo in bus tickets. That's ~750$/mo.

Nowadays, when two bedroom appartments in small remote cities are going for 1600$+, I'm guessing splitting rent is much closer to 800$. That doesn't leave enough money for food, transportation, and communication methods. Heaven forbid you get injured or sick.

If it’s useful: Python now has dataclasses, they are very struct-like.

I have mixed feelings about this. On one hand, this is extremely alienating. On the other hand, I respect when devs reject features to keep their code simple.

I don't think this has anything to do with graduating from berkely, I'm a hobo with a keyboard.

You can tunnel wireguard from a local server to a cheapie DO droplet for about 5$ USD/mo. Only one ipv4 pre dropte though. I read a blogpost that mentioned a free tier cloudflare service for public ips, but have not investigated.

I love xneko, it's adorable.

Thank you!

Almost certain I’m doing it wrong (hobbyist), but most versions of vs studio have some kind of cli interface for installing workloads. I’ll fight with that until I figure out which includes the cli compiler tools. Write a script to automate install. Afterwards I’ll use a build system that calls vcvarsall.bat and perform the build from the cli.

I agree, it feels clunky and bloated compared to what I’m used to (especially if multiple vs studio versions required) but it gets the job done.

I’m very curious what workflows look like for people that know what they’re doing when building c/cpp on windows.

This is what I hope for. I expected that eventually the right job would expose me to a community with overlapping interests. So far I have been fairly unsuccessful.

This is interesting, since I normally fall on the “let’s keep this approachable” side of things - but in this case I disagree.

Maybe I’m just old, but I found using the tools directly very comforting. Learning some static html in a computer camp in notepad.exe was approachable and empowering. I could do it anywhere. I don’t think connecting code to files or compiling it yourself (in simple cases) adds too much complexity while learning.

The first time I opened vs studio I was terrified. I was suddenly not in control of my project. What if I bork it? What if there is an incompatible project change? I think these tools are fantastic and should be used, I just also think learning your toolchain is useful. Disclaimer - I learned these at my own pace, outside of the pressures of a classroom.

1. Hardware driver support in Linux/bsd. I’ll never suffer another broadcom wireless nic.

2. Accessibility of hardware. Is it easy to open and swap parts? Or do you need to dismantle the whole thing?

3. Availability of replacement parts, and history of availability. Ram/HDDs/NICs are universal. Screens, keyboards trackpads are not.

4. Runs off battery? Or adapter when plugged in. In a few years when the battery is toast, will this be a brick?

5. Everything else.

I haven’t tried this yet, but I’m very excited about this. Virtualizing MacOS is extremely painful, and windows is not fantastic. It would be wonderful to be able to quickly jump in, and build and test a program without a lot of preparation. Thank you!

This is really interesting! Thank you so much!

Baikal is pretty nice as a cal-dav/card-dav server with a UI. I can sync it with gnome evolution, thunderbird, an iphone, and android (but required an app).

I haven’t tried it yet, but I’m curious about caldavzap. A web calendar UI that syncs with caldav.

There’s a neat tool called vdirsyncer that keeps a local offline copy of your contacts/calendars that works with it as well.

> great communication isn’t just about what you say, it’s about what other people hear

This is very smart.

That's a good point! If you have your own user account you could dump your .vimrc on there.. but maybe you don't want a lot of vim plugins on a server.

Now that vscode has a plugin that uses your local setup to edit files over SSH, my argument is a lot less compelling. Even at home, I have a lesser vimrc I provision to servers - I found it hard to justify installing treesitter, linters, etc. on a server where I'm mostly dealing with json/yaml/shellscript.

Agreed, I like (trying) to understand as much as I can about how my environment works so if/when something breaks I only need to learn the last 30% in a crisis, and I'm already familiar with the core. It doesn't always work, sometimes there is just too much.

It's usually useful, at least in some abstract way to the team. It felt essential when I worked alone and was accountable for everything.

I guess it depends on your definition of an IDE, and where you're most comfortable/productive. I see a lot of posts about autocomplete, refactoring, linting, tooltips, tests-by-cursor/file, snippets. Thanks to a very friendly plugin community, you can get all of these in vim, emacs etc. I like vim, and it has nothing to do with hubris.

For me it's mostly about:

1. proximity to the terminal: I find cli tools very useful for most of my daily tasks. Using an editor puts the terminal first, and my editor second. One-off tasks are a tmux split/tab/session away and everything is neatly organized.

2. consistent interface: Working with a terminal is neat because everything is text and it is composable. Working in vim, all menus are just buffers - you can navigate them the same way as you would your code. Searching, navigation, jumping between windows/menus, filtering -- everything stays consistent.

3. quick n' dirty workflows: If I identify a task-specific workflow I want to improve in vim, it is pretty easy to drop in functions and/or keybindings to do what I want. The interface was built in a way that makes this easy. Writing a plugin for visualstudio, or jetbrains etc. requires knowing a lot more about the editor you're working in and how it's built. Maybe it just feels that way to me.

4. 0% adjustment when working over SSH: tabs, splits, etc. both in my editor and terminal are identical in an SSH session. No discomfort. Mostly useful at home.

5. low distraction: This one's personal. IDEs are intimidating, hundreds of buttons, menus, logs prompts all fighting for your attention. If I click through a deeply nested menu I often forget what I'm doing - especially if there is a fire. Functions and Muscle memory works for me. It clearly does not work for everyone.

It depends on the production. I think this was especially true on US/CA productions while everything was predominantly hand drawn in the 80s/90s. You'd have key-frame animators that laid out the actions, and in betweening would be outsourced. I'm sure it is still done now, especially for TV where the budget is tighter. It's a tricky business, I empathize with owners that want to make the situation better but need to compete on bids, and employees (if that) having difficulty making rent on the frames they can get approved. Like with code, you have to love it to stick with it.

I have no idea what it's like for anime. This is subjective - but I think the quality is usually much higher. I'm not sure how it is done.

This is so exciting. 1st tier support!

Thank you so much for this post!! God I wish I had a CS degree, this looks like so much fun! One day, maybe...

I have a linux phone, and I love it. I love being able to provision it like a server. I love that I can write applications in just about whatever language I want. True, there is a lot of room for improvement - but I'm a programmer, it's a great excuse to try out some new things and learn about cellular networks.

Thank you! I am very excited to try this

This is positively brilliant.

khal is excellent. I've been using it alongside vdirsyncer for a couple of years now. I recommend aliasing 'khal calendar' to cal - a quick look at your day, and upcoming events.

I also highly recommend khard, which manages contacts.

Yes, certainly. It does not need to be complicated, a little bit of automation can go a long way. If something is tedious, try to automate it. It's faster, more consistent, and frees you up to tackle other fires.

Some examples:

* publishing

* converting between file formats

* simple compositing pipelines

* sending/archiving files

* validation

* organization

* tracking (approval/completion)

* script repetitive tasks in programs to shelves or hotkeys

My first "useful" script was pre-composing an email that sends following a successful FTP send. My second was a helper to relink project mediafiles (which might be on another's desktop) as relative paths so I could open them on my computer. As you scale up, your tools will likely grow more formalized - writing code to glue programs filetypes and departments together, tracking, approval, publishing/rendering pipelines.

Personally, I enjoy changing colourschemes based on where I'm working.

Outside on the balcony? Xterm/vim with white background. 11pm in the livingroom? Xterm/vim with dark background.

I usually have a browser open when I'm coding, so being able to invert the colours is useful for me. If dark mode isn't dark enough, I wrote a Qt script to overlay 50% black overtop of all screens. Does anyone do this to preserve battery life?

I was a commercial artist for 10 years. The same is true of art. In the visual art world everything boils down to contrast. It may be colour, composition, sequences of shots, silhouettes, animation, or otherwise - but at the end of the day everything boils down to contrast. There is nothing mystical or romantic about art. At the end of the day, it is just a set of rules of manipulation/communication. I would say the same about programming. I find programming more interesting and engaging, but that's just me.

I'm so grateful this happened over the weekend, when I had time to respond. My girlfriend woke me up and told me the CPU-fan was going crazy in the living room. I realize this isn't the case for everyone. I extend my deepest consolations to those affected.

You can use salt over SSH, but it is not the default.

You may have been lucky, but that was not the case with everyone. Some of the entries appear to be missing, but last night someone setup a honeypot and was posting what they saw.

Adding keys to /root/.ssh/authorized_keys, scp'ing sshkeys, flushing iptables.

I am of course one of the idiots that had it exposed to the internet. I wouldn't do it with a database, but I didn't think twice about salt. Where was my head!