|
Main Paineframe posted:are most front-end devs unemployed or something? technically, because their time is worthless
|
|
|
|
|
| # ? Jan 24, 2026 12:38 |
|
leper khan posted:hot take: the gdb protocol is good it’s not though, it’s terrible everything supports it though so everybody needs to support it
|
|
|
|
MononcQc posted:I try to always debug my stuff with mechanisms that are available to run on a production system so that way I'm: only people working on servers need to care about this though people writing software for end users don’t have to worry about it
|
|
|
|
eschaton posted:only people working on servers need to care about this though that's literally you guys and the microsoft guys, nowadays and the company i worked at until a few weeks ago altho despite being boring edutech some of our customers insisted on putting computers with our software inside a fuckin faraday cage so it had to be shrinkwrap-style
|
|
|
|
Flat Daddy posted:on the react website its like "don't use this unless you need it, and even then only use it where it's needed." on the redux website it says "you sure as gently caress don't need this.... but just in case here you go". uh, the web browser itself makes a transition when a user clicks a link why would there need to be JavaScript involved in that at all
|
|
|
|
eschaton posted:uh, the web browser itself makes a transition when a user clicks a link because the new thing is to pretend that browsers are electron with weird constraints
|
|
|
|
eschaton posted:uh, the web browser itself makes a transition when a user clicks a link you must be new here
|
|
|
|
Kevin Mitnick P.E. posted:because the new thing is to pretend that browsers are electron with weird constraints Electron is haraam
|
|
|
|
eschaton posted:uh, the web browser itself makes a transition when a user clicks a link because javascript is the future, maaaaaaan
|
|
|
|
cant wait for browsers disable scrolling by default and just expect people to implement it in javascript
|
|
|
|
INFINITE SCROLLING
|
|
|
|
gently caress infinite scroll and gently caress sites that implement their own smooth scrolling when every mobile device already does that and it's so annoying on desktop browsers that I already turned it off gently caress you site
|
|
|
|
web developers who reinvent any kind of browser-supplied UI control should be stabbed in the nuts
|
|
|
|
web developers who break the back button should be sewn in a sack and tossed in the loving sea.
|
|
|
|
|
My favorite feature of infinite scrolling is when you visit another page and then try and hit the back or forward button, it doesn't even have the courtesy of remembering the loving spot on the page you were at.
|
|
|
|
most terrible site I’ve seen so far had one page and a huge JavaScript that waited on the user clicking. depending on what text your cursor was over when you click decided how the page changed. there were no buttons so back sent you back usually to the blank page your browser opens with
|
|
|
|
hailthefish posted:web developers who break the back button should be sewn in a sack and tossed in the loving sea. oracles poo poo stack of peoplesoft related piss break the back button so badly I want to scream nothing is a link, it's all Javascript functions, the url never changes, lord help you if you hit the back button out of habit, you're all the way back to the first page
|
|
|
|
eschaton posted:only people working on servers need to care about this though Yeah that's fair. I guess what I'm saying is that if you're working on server software, operators are some of your users as well and so you should get used to their workflow the same way understanding the end users' is important as well.
|
|
|
|
cjs: diagraming in TikZ
|
|
|
|
|
code:what the actual gently caress
|
|
|
cinci zoo sniper posted:cjs: diagraming in TikZ
|
|
|
|
|
just learned about functional css/atomic css holy poo poo, it is absolutely the worst css-related idea I've ever heard though now that I think about it, I can't think of any good css-related ideas
|
|
|
|
Main Paineframe posted:just learned about functional css/atomic css the one where you make someone deal with the css
|
|
|
|
like the core idea of css (separate appearance markup from actual content, set once and apply everywhere) is good, it's just everything about actually using it is lovely
|
|
|
|
|
Powerful Two-Hander posted:
xml ladies and gentlemen
|
|
|
|
Main Paineframe posted:just learned about functional css/atomic css The best CSS-related idea I've ever heard is BEM, whose core concept is "avoid, at all costs, the cascade".
|
|
|
|
ctps: just found out that a "clever" algorithm i wrote in 2016 has been producing subtly incorrect results all along and i don't know how to fix it the good news is nobody else has noticed yet!
|
|
|
|
how much functionality depends on the mistakes?
|
|
|
|
i don't think anything is going to be relying on the incorrect behavior, if that's what you mean. fixing it might lead to a few inconsistencies in existing data but once it's fixed i can detect those and they won't be hard to resolve if any of them even matter just ... ugh. it's a graph thing. gonna have to break out the pencil and paper and reason about it like some kind of caveman
|
|
|
|
Doom Mathematic posted:The best CSS-related idea I've ever heard is BEM, whose core concept is "avoid, at all costs, the cascade". this is even better https://adamwathan.me/css-utility-classes-and-separation-of-concerns/
|
|
|
|
the whole notion that css and html are "different concerns" is just insane to me this whole idea of BEM and everything around it is manual busywork that finally (seems to be) addressed by web components interested to see how "the frontend community" will mess up those, though
|
|
|
|
akadajet posted:xml ladies and gentlemen displaydata and rawdata are supposed to be representing the same data point
|
|
|
|
cinci zoo sniper posted:cjs: diagraming in TikZ lol
|
|
|
|
ctps: loving around with protocol buffers and gRPC for some special one off nonsense poo poo I'll have to do at work, it seems pretty neat
|
|
|
|
Sagacity posted:the whole notion that css and html are "different concerns" is just insane to me It didn't necessarily age the best in terms of style, but back in the mid-2000s, it was a pretty cool demo of the ideals of separating presentation (CSS) from the semantics of the data itself (HTML). And all of that poo poo worked on most browsers in a day where IE6 and IE7 were very common still. The ideal of separating them suffered a whole lot more when JS became a much bigger deal, and then you had one thing trying to eat at the structure and presentation and interaction of the work, so now you use React and embed everything in JS. MononcQc fucked around with this message at 15:56 on Nov 22, 2018 |
|
|
|
the css zen garden always seemed more like a 'party trick' to me then something actually useful i mean, i think they also wanted to argue that css and html were 'separate concerns', but then in order for it to work you'd have to author your html in a VERY SPECIFIC WAY to make it work with the css: the structure of your html is dictated by the limitations of css, so they are not separate at all
|
|
|
|
css and html being separate makes sense if your divs and spans represent hypertext documents where the semantics are straightforward and the styling is purely an aesthetic matter. the separation makes much less sense when your html elements are being abused to simulate the widgets of a proper desktop gui toolkit. i.e. css = good for data, bad for code
|
|
|
|
akadajet posted:xml ladies and gentlemen Better than json. The data is still garbage but at least I KNOW I can parse it
|
|
|
|
Soricidus posted:css and html being separate makes sense if your divs and spans represent hypertext documents where the semantics are straightforward and the styling is purely an aesthetic matter. if your HTML doesn’t represent hypertext documents where the semantics are straightforward and the styling is purely an aesthetic matter, then what you’re doing should not involve HTML, you should write a native app
|
|
|
|
|
| # ? Jan 24, 2026 12:38 |
|
eschaton posted:if your HTML doesn’t represent hypertext documents where the semantics are straightforward and the styling is purely an aesthetic matter, then what you’re doing should not involve HTML, you should write a native app
|
|
|

































