Hmm, I'd have a look at the yt-dlp source code. I think it can download subtitles/transcripts (and list them). The process does take a few seconds though.
I was just going to chime in with this. I don't know the details of their implementation, but I get transcripts with every video I download using yt-dlp (if it exists which it does 99.9% of the time).
am I able to download all the transcripts of each video from one channel? I was planning on doing this with a few channels. If this is even possible with YT-DL.
Hmm, youd need to first get a list of channel videos and then iterate thrpugh them, probablu with a script. Yt-dlp might support getting the videos in a channel, idk. I do know that it can download while playlists... Perhaps try passing it the channel url and seeing if it treats that as a playlost.
YouTube sometimes made it hard to find, but all channels do have an all videos Playlist. I think he button is on a profiles video page now. I don't know if yt-dlp can do only transcripts but I'm sure it can download all videos with transcripts included.
Yeah, it's definitely a very unique approach I haven't seen before. I've been using the "honeypot" method for years, which has been working surprisingly well.
Apparently the rate of users not using JS is about 0.2% (and has been that way for 10 years), so just applying this solution the the large margins as heās doing, Iād probably just make an alternate message saying āplease enable javascript to contact meā and let that be that.
Eh. These sorts of metrics aren't always accurate. And the source company did the study in 2016, which was a very very different internet, and doesn't go into detail about how they were able to determine this number. I would take that with a grain of salt. I agree that just having a notice somewhere is better than not, though.
Sure, I was just curious and looked it up, thatās the first link I saw. I guess the question is ā is it better to theoretically annoy real users who arenāt using JS (and how many are there) or is it better to frustrate and annoy lazy spammers (and how many are there?). On my own sites I really rarely get non-spam email. Iād be fine making a random 10-45 second timer on my contact forms doing this, no one needs to contact me in under 10 seconds on my websites.
I've been waiting so long for :has(), and had no idea it was finally implemented. This is huge for userstyles. Now I should be able to hide retweets and inline ads from Twitter with just a couple lines of css.
I'm glad we can use logical properties now. Dealing with systems that support both LTR (like English) and RTL (like Hebrew and Arabic) languages used to be a pain because we had to have a build script that generated a second CSS bundle with everything flipped (eg converts margin-left to margin-right, border-left to border-right, etc. Logical properties make it a lot easier.
I love the gap property for flexbox... I use that one all the time. Easily solves the "I need padding between all these items, but no padding at the start or end" use case.
I'm going to be honest. I like this thread. Not only is the article long and "thorough" (whether you agree with this form of thoroughness or not) but the responses are too.
I can appreciate what the author is trying to express. I also related to how he's trying to express it because it's very similar to how I try to explain my opinions, shower thoughts, meanderings....which typically earns me eyes glazing over from my conversation partners haha.
I have many many thoughts on everything being discussed here, but rather than contribute, I'm going to sip on my coffee and keep reading.
P.s. I'm liking PD better than Reddit. Actual conversation happening.
SNEED FEED SNEED'S CHUCK FOR FREE FLOYD HOT POCKETS CHUCK'S FLOYD CLEAN IT UP CITY SLICKER CHUCK'S CLEAN IT UP SUCK FEED JANNIES CITY SLICKER SEETHE CITY SLICKER CLEAN IT UP DILATE SEETHE DILATE SEETHE FUCK SNEED'S I CAN'T SUCK FLOYD FLOYD HOT POCKETS COPE SNEED'S FOR FREE CHUCK'S FLOYD COPE SUCK FUCK SNEED CITY SLICKER I CAN'T FLOYD SEED DILATE SUCK SUCK SNEED SNEED'S JANNY
CSS is a programming language because thatās what youāre doing when you write it; youāre programming the applicationās presentation logic.
It's as if he wants to get into a philosophical debate about what programming languages are.
Frontend is hard and it's made unnecessarily hard by HTML,CSS, and Javascript. I swore off of frontend due to the evergrowing, unnecessary complications.
What I'm looking forward to is web apps written in a single programming language with no javascript knowledge necessary at all. There are rust frameworks that generate the JS boilerplat to load WASM. Some use the DOM to make their UIs, some insert a canvas and use WebGL, some generate HTML in the backend and replace parts of the live frontend with that, but my favorite is when there's no HTML, CSS or JS in sight.
As for the devaluation of frontend, I always found it weird that frontend devs were paid less than backend devs. I respect frontend devs for being able to do what I can't. We're in this together. Pay us all a good wage. We're workers and have to stick together.
I think most of the arguments here are kinda ridiculous and poorly thought out. A lot of them also sound pretty imaginary and made-up. For example:
To assert that frontend languages are not programming languages is to assert that what one is doing when writing them is not programming, but something else. Something different.
Somethingāperhaps not explicitly spoken, but undeniably impliedālesser.
Basically, he's arguing that everyone who thinks HTML/CSS isn't a programming language is wrong, and then the only reason they feel this way is because of a prejudice against front-end developers. I think this is really just a wild leap in logical reasoning, personally.
(No mention of Javascript/Typescript here by the way.)
If you wanted to find the dev specialization with the most people who arenāt cishet white males, youād pick frontend.
Do we honestly believe the language around frontend is different purely by mere coincidence?
... yes? His argument that HTML/CSS should be considered programming languages is honestly quite weak. Couldn't that be the reason instead?
Certain pursuits are validated with importance, dignity, and honor.
... we relegate others to the role of the sidekick - even though their labor is no less important, and they do at least as much to push the work toward success.
Who the hell is making these groupings?? Front-end developers compared to nurses? Software engineers to doctors? And software engineers being held in the same light as CEOs... wtf???!?!?
(Surely itās a coincidence the first group tends to be more male than the second.)
Once again, he's attributing his feelings with prejudice when really, I think his arguments are just very poorly thought out.
Other forms of development are generally considered serious work. Theyāre important. Theyāre real computer science. (Computer science itself being a higher level of things weāve decided are real, serious, and importantāmaybe not quite as much as medicine or law, but then again, maybe so in some circles.)
Again, I don't see anyone arguing or claiming this. I'm sure the author would argue that just because we don't say it aloud, but it's just implied, but I honestly just think no one says it because it's just silly.
Writing CSS seems to be regarded much like taking notes in a meeting, complete with the implicit sexism and devaluation of the note takerās importance in the room.
Though critical to the project, frontend work will quite often be disregarded by those who consider it beneath them (usually men, and usually only tacitly, never explicitly). Itās not serious enough; not important enough; not real enough. Too squishy. Like soft skills.
Once again, just unfounded accusations of bias. "You didn't say it, but I'm telling you that you said it anyway."
Their [software engineers'] output is easily measurable. A new API feature; a more efficient database; crises averted and crashes prevented. They go on charts and get presented to board members.
Board members couldn't give less of a shit regarding what software engineers do. We're considered a cost that they'd love to get rid of as much as any other position. Look at all the AI hysteria going on right now, like Nvidia's CEO telling people not to go into software because it won't exist anymore. Again, I have no clue where this guy is getting his ideas from.
If our job title does include the word āengineer,ā it will almost certainly specify what weāre engineering. Itāll be UI engineer, or frontend engineer, or maybe the newer (and arguably more fitting) design engineer.
But itās probably not āsoftware developerā or āsoftware engineerā without any other qualification. Because that, tacitly, is not what we do.
Completely disagree. Front-end development is a subset of software engineering. He even admits this as much:
Sure, this is nuance of language and these titles serve to disambiguate. I get that.
but then he goes on to dismiss that by saying "that's not really it though, it's really because we're not considered real engineers":
by definition, somehow what we do isnāt seen as software engineering. Itās different than that. Itās softer than that.
By what definition exactly? He just explained the reason for the difference in terms above, but then goes on to say that's not really it - the real reason for everything bad is (what he perceives as) negative bias.
There's a couple interesting ideas in here. He makes a good point that layoffs on the front-end are more likely to hit underrepresented classes, though there's not much that can be done about that. Layoffs are happening everywhere, and DEI is probably not what's on CEOs' minds when they make those decisions. And sure, there are unrealistic expectations at times, but that happens everywhere, not just in the software industry, but in pretty much any labor scenario.
But overall, I think this guy has major issues with his self-perception. Pretty much all of his arguments are predicated on very poorly thought-out or straight up imaginary ideas. And blaming everything that's wrong with his perception of front-end development on the white male hierarchy is just... I can barely even find words for it... nonplussing? I think he figured it out by the end of the article:
Maybe Iām feeling sorry for myself. Maybe Iām just a little depressed right now. Maybe I have an inferiority complex and Iām projecting it on everyone else.
I'm pretty sure it's all of those.
I wish this guy the best. Shit is hard right now. But I'd be a fool to say that I agreed with more than 10% of what he's trying to argue.
I wholeheartedly agree: the article is just plain stupid.
What I find more amusing is that front-end work ends up being the most critical work in any user-facing application. Apps can still lumber around if big chunks of backing services are down, but if a page is rendered poorly or a button is showing up weird, or if text is missing in a place everyone looks at, that's automatically a SEV1 right there.
Web Development
Hot