sql as the language executed by the db hasn’t changed notably, but I do think there’s been significant developments in ORMs. for a lot of developmers sql is now just an intermediate target
- 0 Posts
- 21 Comments
more directly, sqlite was originally for tcl which is why they share the semantics.
also I’d argue that sqlite is a bigger contribution than tk, but I suppose in a more roundabout way
NixOS, plasma rn but sometimes jump to sway. I’d say distro is more relevant. for the most part I just have an editor and a browser open, DE doesn’t change much about my workflow. NixOS definitely does though
chosen by my team, company at large doesn’t care but it’s nice for everyone to be on something consistent. company devices
NixOS is a nice balance of the two
I generally just copy my personal setup, which I’ve spent a decent amount of time on, but because I enjoy it
not particularly, but nix supports all of the big ones
language and stack a little bit, it’s all stuff that has good integration with nix. we deploy nix containers and then have consistent environment everywhere without having to work in a container. my team is a pretty standard team maintaining some full stack web stuff
brian@programming.devto Programmer Humor@programming.dev•[ComiCSS] Benefits of Tailwind2·3 months agoI’m saying we weren’t taught when react was the way people wrote sites. if I was writing a site with pure html, css is great, especially modern css.
but if I’m already using react and their abstractions, opinions on that part aside, I’d personally rather lean on the react component as the unit of reuse. tailwind removes the abstraction that you don’t need, since many people in react tend towards one scoped css file per component with classes for each element anyway
at this point I’d be more inclined to say for many sites the api and data fetching things are the content and html+css is presentation. csszengarden is cool but I haven’t seen the html/css split help an end user, or really even me as a developer.
brian@programming.devto Programmer Humor@programming.dev•[ComiCSS] Benefits of Tailwind1·3 months agoinstead of using classes you just use whatever your ui library provides for reuse. stick a classname string in a variable and you have a class. use a component and it just contains all its styles.
unless you mean that if you look in the inspector you see a mess of classnames. I don’t have a solution there
brian@programming.devto Programmer Humor@programming.dev•[ComiCSS] Benefits of Tailwind2·3 months agoshadcn is the primary one for react at least. they’ve done a great job filling the space where you’re trying to build up a design system but don’t want to start from scratch, but they’re great if you just want prebuilt components too
all the components build on something else like radix, and are pretty simple themselves. normally just the radix component with styles. Installing a component just copypastes the source into your project at configured locations.
if you’ve ever fought against something like mui to get it to fit design changes or change specific behavior, shadcn is great. at some point the extension points of a library aren’t enough, but if you own all the code that’ll never be a problem.
brian@programming.devto Programmer Humor@programming.dev•[ComiCSS] Benefits of Tailwind62·3 months agoexcept we generally use higher level abstractions now, like component based frameworks. If you’re writing raw html with tailwind and no library you’re doing it wrong and css is a better fit.
well written straight css ends up building it’s own tree of components. if you’re using react too you’re either only selecting a single component (inline styles but have to open two files) or writing good css (duplicating the component hierarchy in css).
tailwind is just the former but better since it encourages using a projectwide set of specific sizes/colors/breakpoints and small scope, the two actual problems with inline styles after organization and resuse, which react etc solves.
brian@programming.devto Programmer Humor@programming.dev•When people ask how your plan for life is going...4·3 months agoI’m sure all of them are just cherrypicked hotfixes from main tho
repr is generally assumed to be side effect free and cheap to run, so things like debuggers tend to show repr of things in scope, including possibly
exit
also then it behaves differently between repl and script, since repr never gets run. to do it properly it has to be a new repl keyword I imagine, but I still don’t know if I’m sold on the idea
brian@programming.devto Linux@programming.dev•Why Microsoft open sourced PowerShell and ported it to Linux1·4 months agothere are other shells that have all the nice powershell things without the weird stuff (at least for not windows people), like nushell
although I wouldn’t be surprised if powershell was the thing that started the trend of better shells
ones that can run cli tools do great, they just use npm
because with things that the compiler does, like padding for alignment, it frequently takes up more space than that. that was my argument the whole time. what til are you talking about? I’m talking about an extra layer you’ve decided doesn’t count. ofc sizeof bool will be a byte in all of those languages.
a bool taking up a single byte is a fantasy that those languages use because developers generally don’t need to think about all the other stuff going on.
a bool is actually a single bit, the rest is all padding
c++ guarantees that calls to malloc are aligned https://en.cppreference.com/w/cpp/memory/c/malloc .
you can call
malloc(1)
ofc, but callingmalloc_usable_size(malloc(1))
is giving me 24, so it at least allocated 24 bytes for my 1, plus any tracking overheadyeah, as I said, in a stack frame. not surprised a compiler packed them into single bytes in the same frame (but I wouldn’t be that surprised the other way either), but the system v abi guarantees at least 4 byte alignment of a stack frame on entering a fn, so if you stored a single bool it’ll get 3+ extra bytes added on the next fn call.
computers align things. you normally don’t have to think about it. Consider this a TIL moment.
sure, but if you have a single bool in a stack frame it’s probably going to be more than a byte. on the heap definitely more than a byte
I mean, that sounds sorta like JWTs which are used commonly enough for this type of thing
why would you need to salt long random strings?
also if you salt them you have to have an id too so you can look up who’s api key it is. otherwise you can just look up the key hash to get everything
why would you need to salt long random strings?
also if you salt them you have to have an id too so you can look up who’s api key it is. otherwise you can just look up the key hash to get everything
things that store it as word size for alignment purposes (most common afaik), things that pack multiple books into one byte (normally only things like bool sequences/structs), etc
yeah, ofc it should only be a curated set of errors where the consumer can do something about it. unknown errors should just be opaque 500s