css_apologist

xpath is so fucking cool

i can understand why it failed for general use, but shit like this revives my excitement

q: i'm not an expert, this looks like it extends xpath syntax? haven't seen stuff like the /map is this referring to the html map element? or a fp-style map?

technically jailbreak stores count, but not practically comparable

Once we grow up as a nation and legalize competing app stores on native Android and iOS you can try to make this point

However, the alternatives are currently illegal, so your point doesn't hold

does it not bother you that your company is not useful to society?

on Shadcn's codegen

I think this is necessary since we need to regularly modify components to suit our needs.. (I've dreamt of extending this kind of approach to libraries for a long time)

HOWEVER

there has been an elegant solution to this problem for 30 years - CSS

CSS tooling lags behind, but from a technical perspective CSS is superior to this component library approach in almost every way

i'm interpreting this in the reverse

if dev tools can only be "monetized" by being bought out, it does not feel sustainable on any level

we will see companies attempt to do things like close source these projects, go subscription based, or just straight up drop support

there is no incentives for cloudflare to make astro better, or even keep it around

same goes with bun, svelte, and i'm sure countless others

people act as if this is an individualist problem, but that ignores all the facts

the first place to think about serious change is city planning since the invention of cars & then suburbs

we used to be forced to live next to each other, walk and see each other

it turns our car based city planning doesn’t work on any level if you look at cities which didn’t go all in

this article is about humility

its odd to me that it takes time for people to develop this, i had it very early. I understood the painpoints of business leaders, and technical debt early on.

However, i can no longer excuse the state of things, its pathetic that we just learn to accept that we will always consistently deliver trash, and it is _much harder_ to fix it than to just let it fail

i do not see a solution to this in the current fascist structures we work in

first let me say i applaud you for experimenting and doing something unconventional

- thoughts as i was reading this -

ok, so we're programming via an AST vs syntax

I think this is interesting, however there's notable downsides - verbosity, dom bloat & debugging

A potential upside to this is very odd but interesting meta programming capabilities, since the code should be able to inspect & modify itself fairly easily by inspecting the dom

I am inclined to distrust the claim that this reduces complexity as most of the actions are mutation heavy directly to the dom, and the stack based programming is something i struggle to practical examples where it is a significant improvement to mainstream strategies

learning curve isn’t always a bad thing

to effectively critique a language you must understand the design trade offs made

this should be required by law

it's like writing code in my notebook, which i find extremely beautiful

modern editor features are very loud, and you don't notice it until you turn it off

that being said, this is not a good strategy for work editors

this is news to me, how does this work? who is getting paid?

> Are Java developers just not as competent as Ruby programmers?

years ago a senior developer close to me said "when screening interviews, if i see rails i throw the resume in the trash"

so ironic how trivial/stupid these language-based judgements are

> With one hand they do so much to protect consumer rights for us citizens, but with the other hand they build a survailance state.

You say this with no irony as an american..

CSS is hard to love, but its worth it

there’s a deeply elegant language hidden in there with unbelievable support for generic programming, however it is practically impossible to do that in a component system and the current state of CSS editors

i find it hysterical we design component libraries where the only acceptable way to extend the design of a component is add a prop when CSS has a perfectly elegant way to do this without muddying up the component source

not to mention the dark arts of encoding show/hide/position/more logic that is often done in js

it is the saving grace of the web, but never has been realized

LLMs are really showing how different programmers are from one another

i am in your camp, i get 0 satisfaction out of seeing something appear on the screen which i don't deeply understand

i want to feel the computer as i type, i've recently been toying with turning off syntax highlighting and LSPs (not for everyone), and i am surprised at the lack of distractions and feeling of craft and joy it brings me

nested is the main one, however i remember cases where a rule couldn't be parsed and the rest of the file went fuckidy

this is pathetic, and really shows how much of a shitter css tooling currently resides in

css syntax highlighting has been broken in vs code for years now.

how in the world is this possible in THE web dev editor?

its common to santize html string to parse it and remove/error on script tags (and other possible vulnerabilities)

i wonder do people not do this with svgs?

is santizing SVGs hard, or just everyone forgets they can contain js?

(i do like innovating on this btw)

here's a basic CSS starting point

    :has(.pnp-picked) .pnp-item:not(.pnp-picked):not(:last-child)::after {
        content: "[place]";
    }

i was expecting when i click pick, that a "place" button would appear on each other item, or i could click on a row

OR possibly highlighting the spots between rows either with a line, or "place"

i think that's a much more intuitive & reliable ui, and would be an improvement on drag n drop. or a supplement to it

honestly both the react haters & the htmx haters are wrong on this

if you care about have a solid UI, you should learn everything

you should learn css, react, svelte, vue, rails, tailwind, html

if you don't and you say you actually care about your UI, your opinion is actually irrelevant

    const body = JSON.stringify({
        model: "gpt-4.1-mini",
        messages: [{ role: "user", content: "hii" }]
    });

    const r = t.fetch("https://api.openai.com/v1/chat/completions", {
        method: "POST",
        headers: {
            "Content-Type": "application/json",
            "Authorization": `Bearer ${API_KEY}`
        },
        body
    });

    const json = JSON.parse(r.body);

.. no async? i wonder how they are doing this & how they plan on more js interop

i want this to be true, however i am not confident

no, social media did not kill it :facepalm:

mass de-regulation, tax avoidance, effective end of anti-trust killed it

social media was just the tool-of-the-day to break democracy

.. or enforcing & updating anti-monopoly policies

when are we going to finally give up on the concept of the app store?

it is not efficient, it doesn't incentivize high quality products, and the web proves that security / safety can be done in an open way.

this is all true, especially for those of us who make no where near that much