Say, you have a software project. To do some operations more quickly, you write helper scripts. Think `build.sh`, `download_dependencies.py`, whatever. You may use them yourself or in CI.
What is your directory name of choice for these scripts?
@kytta I prefer putting this kind of stuff in a Makefile 🤷♂️ These actions are often interconnected, e.g. package requires build, build requires fetch_deps, etc. Makefile makes it trivial to manage and good for discoverability.
Coming back to a #JavaScript project after 1–2 months of not working on it. `pnpm up` reports ~150 updated dependencies out of 875. And those are just minor/patch updates.
I feel like JS developers get punished if they don’t release daily 🙄
A few weeks ago, I’ve written a small essay about modern #Python tools (like #Ruff and #uv) and things I dislike about them. I wanted to first redesign my website before posting it, but nah, that would take too long of a time 😂
I love listening to #podcasts, but it's not my number 1 source of entertainment. As such, I only get to listen to them when I can't watch videos or write code, which is usually my job commute. When I started working full-time, I finally got the opportunity to process my listening queue.
Well, 2024 hasn't been that productive, so far. I started working remotely, then I went on a holiday, and then I got sick, so I'm back to 100 episodes, 3+ days of listening 🙃
The #JavaScript ecosystem is number 1 when it comes to volatility and fragility. Try building a project made in 2014, and you’ll know what I mean: Gulp doesn’t work, libsass doesn’t compile, etc.
Well, today, it was dethroned by #Android (or, should I say, #Gradle). I have spent *hours* to revive a project from 2018 to just bump the targetSdk version. 90% of the time was spent with Gradle not working, even when presented with the same JARs as years ago!
Having said that, #C is probably my favourite language/ecosystem combo. Yes, there is no simple `npm install`, and build systems can be cumbersome, but I love how a complete ecosystem bootstrapping is basically `brew install gcc make cmake autoconf`, compiling is fast, and subsequent builds even faster. And you can compile most code from 30 years ago without much hassle.
A question to my fellow #Web developers and designers: How do you handle checkboxes and labels with #RTL? It’s clear to me that their position should be flipped (see image by @shadeed9), but what are your preferred ways of achieving this (with static HTML)? Is `flex-direction: row` a valid approach, or are there other ways I’m missing?
@kytta depends on how you implement it: This particular one could just be an inline checkbox, which wouldn’t need any thinking about to put it to the right.
But otherwise flex-direction row together with semantic margins/paddings (padding/margin-inline-start/end) would usually do the trick for me.
@kytta inputs and labels are both inline elements, so a browser already has rules for choosing between RTL and LTR. You can just use dir="auto" in HTML, and let the browser figure it out. Or set it explicitly with dir="ltr" and dir="rtl".
- the rooms need to be bigger, since I couldn't visit all the talks I wanted to - the conference should be longer, since I couldn't visit all the talks I wanted to - the ones I did visit were incredibly fun, and I learned a lot! - #JohnMastodon exists
What began with an 8-hour-long train journey, ended with a wonderful stay in pretty Maastricht. If you ever find yourself travelling from Germany to Brussels (whatever the reason for this may be :blobcatfingerguns:), consider staying here for a day or two. But please, don't be like me, take an ICE and not regional :blobcatdizzy:
Hey Fedi, I need help tracking down a website I yet again forgot to bookmark 🙄
It's a collection of badges to mark whether your content is AI-generated, made with the help of AI, or not touched by AI at all. It was CC0, and the logos features three points that would interconnect in different ways based on how much AI was used.
This year, I didn't finish #100DaysToOffload, I haven't finished a single book, and I didn't build anything worth forking.
And still, this was an incredible year for me. I've graduated from my university (still waiting for my certificate...) and got an incredible job. I've been a guest on a podcast! And, most importantly, I've been the happiest I've ever been.
2024 will bring in a lot of new challenges and opportunities, and I'm looking forward to them.
Today's idea: Detect if people visiting my website have an ad blocker enabled, *and if they don't*, show them a popup saying why it's a good idea with a link to install uBlock Origin
Given how popular Logitech MX mice are, also amongst developers, how come nobody has still made a *usable* version of the ‘Options’ software? Reverse-engineer the drivers, make a lightweight daemon and native UI. Are the projects that currently are or have tried tackling this?
@kytta the awful Options software seemed like an increasing security risk and the quality of the mice has gotten worse. That led me to ultimately discontinue my use of Logitech mice about two years ago. The problem is real.
I already have enough unfinished side projects, but I am freaking pissed by Logitech adding AI to their mice (and software). So, I hereby announce that I have started reverse engineering the Logi Options+ software.
My plan is to bypass the installer, re-implement the drivers and daemons and add simple text-based configuration (to begin with). I’ll focus MX Master 3 + macOS + Apple Silicon first (I’ve nothing else to debug on). The licence will be GPLv3-only.
Fediverse, I need your honest opinion on my next crazy project idea.
I am envisioning a CLI app that would give you contact details for people based on their nicknames/homepages. Here are some loose thought about how it should work: https://codeberg.org/kytta/reachout/wiki/Project-idea (~2 minutes; please read before voting)
I want to keep it as ethical as possible, and I want to know whether you think it’s creepy or not, and whether you would use it :D
Gregory's Server
I would put them into the root directory. For additional things that one would run manually, e.g. code generation or validation, I use ./tools.
./build in my mind is where intermediate build artifacts go because that's what Android Studio does.
@kytta I prefer putting this kind of stuff in a Makefile 🤷♂️
These actions are often interconnected, e.g. package requires build, build requires fetch_deps, etc. Makefile makes it trivial to manage and good for discoverability.
But if not, then I'd go with ./bin probably.
@kytta I use “just” instead to build them. Sort of like Makefiles but better.