General statistics
List of Youtube channels
Youtube commenter search
Distinguished comments
About

Anony Mousse
Theo - t3․gg
comments

Comments by "Anony Mousse" (@anon_y_mousse) on "Theo - t3․gg" channel.

I'll keep using square checkboxes and round radio buttons until the day I die. Personally, in that list of prior examples, I like the Win95/98 era checkboxes the most.
28
I think a huge part of why I only ever dabbled in web dev and stuck to systems programming is because I once took a job writing a gallery image viewer for a website and the horrors of adding in every requested feature still haunt me to this day. It was super painful not only centering images but making the entire page clickable when the gallery was active to allow for clicking left and right to navigate and hitting the center to bring up the menu for "fast travel". Now there are so many better methods of doing a gallery, including having a scroll of thumbnails and swipe interfaces, but this was something like 15 years ago. Even loading the images asynchronously was a pain back then.
15
It already is a full blown programming language that people write whole apps to run in the web browser with. Some people even write whole apps that run outside of the browser using various runtimes. It was never intended for that and shouldn't be used for that now, but it won't stop people from doing such crazy things. It's like the various kernel projects that have been started over the years in languages ranging from BASIC to Java. Inappropriate isn't in some people's vocabulary.
13
@joseoncrack It doesn't matter how hard a company vets new hires, as long as they're a malicious state sponsored actor, then they will introduce it and no large company is going to code review well enough to find everything.
7
Banning is absolutely the wrong move, especially as a quick option, and I think Lasse being suspended when he wasn't at fault proves it. Some of the rudest people in open source are the best at what they do, and I can't imagine how detrimental that would be if they had been banned long ago when they got started. What we need is to not trust people that we've never personally met and taken a true measure of. We also need more eyes on projects that are what I would consider keystones of computer usage. A compression library is most definitely one of those. Everything we do utilizes compression these days, even just connecting to the internet. As for the human element of this story, several of the channels I watch did cover that, but I probably watch more Linux content than you since I use Linux, so I can understand you missing that.
7
It's still weird to me that so many projects keep getting made for one of the worst programming languages there is. Hopefully WASM leads to JavaScript being replaced in the browser space. I'd love to see some major browser based apps programmed with C.
6
@spicybaguette7706 Not really a useful technique when major projects that are actively maintained have open issues for two decades. You just never know if someone is actively behind the wheel or not and it's not a bad question. Especially when you consider that a project may be properly maintained but have no commits for a long time because the project is already perfect.
5
For this one, he looks determined. Not necessarily not constipated, but more like he feels the movement and it's definitely coming today.
5
@sub-harmonik Well, that depends on what kind of front-end you mean. I was very specifically referring to web dev, which is the worst kind of front-end development. I still do user interfaces, but now they use toolkits that rarely change and don't have baffling quirks that vary in functionality even on the same OS.
5
@samuelmorkbednarzkepler Now you're just being obstinate. Replacing it would be easy from a technical standpoint. The only thing that's needed from a societal standpoint is for every webmaster to switch to an alternative. Just need one browser to enable that better option, remember VBScript and how it worked, then everyone would have a reason to switch. We already have alternatives getting pushed into the space, complete or not. Even an implementation of Lua would be better than JavaScript, but can you imagine if a new BASIC variant was created for web dev. That would be hilarious.
4
While I can certainly agree that Python is best when you're not really computing anything with it but rather using it to glue libraries together written in better languages, I would still rather use Git than Mercurial. I also think it was a mistake on the Git maintainers part to not work with Facebook. However, I have a possibly non sequitur question for anyone that might know, what the hell does Facebook do that they have more code than the Linux kernel?
4
@FakeRyanGuild Funny, and while it could do with quite a few edits, I'll just point out one: s/rained/reigned/ .
3
@roccociccone597 In other words, use what's appropriate for the case. Of course, that won't stop people from doing what they want whether it fits or not, and I wouldn't be surprised if someone is working on or has already written a kernel in JavaScript. Believe it or not, someone actually wrote one in BASIC.
3
I'd never heard of HIR before, but after a quick search I suppose it makes sense as a buzz term for a transpiler. I would've just called it IR instead of trying to confuse people, because it doesn't matter how high or low it is, it's still an IR. Of course, I also didn't know that React had a compiler they were working on and now I have to go read it.
3
@HappyCheeryChap Only makes it worse that a Go language had already existed before they created theirs too. The first Go developer tried to sue Google and because his was more of a DSL he lost, but I wish he had won and they'd used another name.
3
Another point I dislike. It makes what's happening in the code far less clear than simply using the keyword return. I don't think that's too much to ask.
3
@pokefreak2112 Have to agree, and wish there were more that took pride in their work.
3
@SianaGearz Ah right, so instead of countering what they're saying you prove them correct by merely silencing them. A slapped person can still talk. Of course, we're seeing the negative consequences of your chosen methodology play out in the present day and hopefully we'll learn that it's the wrong method before it's too late.
3
@SianaGearz But most importantly, they can't speak to the project maintainers. So instead of correcting something that's wrong, it's either left to them to fork the project which is likely more effort than they're willing to take on, or let it rot. That would be a negative consequence, at least in a sane person's mind.
3
@lucyinchat No, fork it and maintain it yourself.
3
@SianaGearz That presumes that the community is well functioning. You may not even realize when it's not, especially if you kick out all potential contributors that you don't like.
3
@GeorgeMixalis That's certainly a possibility. And if it is just down to code bloat, then the monorepo is a bad idea because they should probably be paring their codebase down a lot instead.
3
@samuelmorkbednarzkepler While it is currently the language of the web, it wasn't always, doesn't have to be, doesn't deserve to be, and most definitely should be replaced. Does anyone remember VBScript? How about Java applets? Yeah, both sucked, but we still shouldn't be using JavaScript.
2
The only thing good about it is the concurrency because it uses BEAM. It's literally a less effective Rust. I wonder how long he had been working on it because I'm still not ready to release my language, but mine will have function overloading and allow using whatever Unicode characters you want. And I still take issue with the fake inference that modern languages have. let as a keyword to define an object, is just dumb. It's basically a weaker version of the auto keyword in C++ because now you're asking for permission. In my language you can infer by just doing foo := bar; The only reason for the : notation in setting a value in my language is to tell the compiler to create something there. It's just a way of catching mistakes, so you won't be likely to do foo = bar; and later baz = foO; and get a value or error you don't expect. It also works as a conditional guard so you don't accidentally set the value in a conditional. I also take issue with the import systems for every modern language, even C++. If I'm importing a library I expect it to be immediately accessible. So import io; and everything in the io subsection of the library is accessible, but you can also do import io as io; and keep it in its own namespace or import io as fluffernutter; if you want. I also took the approach of inferring meaning in cases where the context tells me what you're referring to, such as enum Color { Red, Green, Blue }; Color c = Green; instead of requiring Color:Green to explicitly get at the namespace, though you can still be explicit if you want. I did the same for switch. switch c { Red: foo(); break; Green { bar(); baz(); } Blue { print( "Green doesn't fall through because it enclosed the case in braces.\n Red does fall through because it designates a section.\n" ); } }. I also avoided the Java style keyword duplication by allowing a modifier to enclose a block or start a section. So say you want to make a group of functions public, just do public: and everything until the next section is public, and you can stack them. I still don't understand why everyone wants to copy Java and JavaScript for function syntax. No need for a keyword, just use a regular pattern.
2
What you said about Watchman is kind of funny. Do you know how the `make` program determines when to rebuild a file? When the source has a more recent timestamp than the binary. It's really that simple. And the same process can be used on Windows by just stat'ing the file. Back when I used Win98 I knew how to use the Win32 API to stat a file and compare timestamps. So if any devs for any project needed to use a third-party program to determine when to rebuild files, they should be embarrassed. Hopefully I'm not calling you out, it's just something I found funny.
2
Agreed. Let the language speak for itself. No mascots for any.
2
Yes, talk more about this subject. I hardly ever do anything with PNG's, and in the past when I needed to save and load images for various programs I just used the tiny library I made for reading and writing bitmaps. I just about had the bitmap format memorized and could write it from scratch, but the most advanced compression they utilized back in those days was RLE. It was a lot handier back then because when I was still on Win98, all of the image formats that I wanted to work with used the bitmap format as their basis. Icons were especially neat because they were sort of multilayered bitmaps where some layers worked as masks to enable transparency and some were for higher resolution images. I don't know if Microsoft still uses those for new programs, but here on Linux you can basically use any image format for anything and icons can be small PNG's if you want.
2
Not if it changes every instance. Can we say modified globals?
2
I wound up doing one in C and just using the standard library with no platform specific code it was about a second, so anyone else should be able to do it too. Java requiring a third-party tool to accomplish what a better language can do as standard is kind of funny. However, the funniest part of the whole video is where you ask if you're a bottom. If you have to ask, you probably are. ;)
2
Ah classic. Microsoft makes everything they buy shittier. Submit a pull request and server error. I await the apologists in the crowd making excuses such as "he entered bad input" as though that's a valid reason for a server to crash instead of displaying a message telling you that you entered something wrong.
2
@SianaGearz Right, so instead of teaching people to harden up and not have mental issues, you keep them in a safe space so that when real life comes calling they can't handle even the slightest wind. Consider how human beings learn and realize your mistake.
2
@SianaGearz You have failed to realize the obvious here. People fear retaliation in person, thus they've learned not to be assholes to others when face to face. If only allowed words, then retaliation requires more words. This is called reflection, for obvious reasons, and is a technique that more should employ.
2
@SianaGearz I'll repeat myself here, but it's truly ironic how many open source proponents are free speech opponents while never realizing that they're the same thing. It's not smugness, but rather experience, that tells me everything I need to know about most people. You've given away too much. And every project that has introduced a CoC is an example of it being bad, you just refuse to see how. If the fall happens in your lifetime, then you'll see all too well the consequences of yours and others actions.
2
It's always the people that say such things who are the worst when it comes to actually respecting others' rights. The funny thing is they say everyone is welcome, but if you espouse even a glimmer of conservative thought they'll kick you to the curb.
2
Completely disagree with regards to Google vs Oracle. The chief reasons being that A) Sun opened the source for the JDK and JVM before Oracle bought Java from them, and B) Oracle didn't even create Java, they bought it from Sun, and of course C) Google didn't copy any code to make their runtime, nor did they call it Java. It has already been established with prior court precedents that you can't copyright an API. Furthermore, logically and morally speaking, copyrights, patents and trademarks should not be transferable. As for Nintendo's insecurities, I always referred to the NES as a Nintendo and the SNES as a Super Nintendo. They should've just embraced that, but they're a shit company anyway so fuck 'em. I really don't know why I bother wasting my time commenting because YouTube either deletes or shadows a good 85% of my comments, and the ones that stick just about never get read anyway.
2
@randymccoy8097 The problem I'm having with it is, what does Facebook as a company do that in a single repo they would have more source than Linux. I would think that a social media company wouldn't require that much code for even the backend of their website. It feels very much like corporate bloat, and that's the only way it can make any sense to me.
2
Not that you'll read this, but I'd actually prefer we just stick with the old works-everywhere formats. PNG's and JPEG's were good enough and if you're using an older computer you probably can't update it to use the newer format because you can't update either your hardware or your software. As it turns out for me, I can't open AVIF except through the browser and AV1 encoded video plays like a slideshow. I have a few means for converting WEB/P, but it's awkward to deal with and I can't really browse my local files if they're encoded that way. However, there are two points that need correcting. The first is that JPEG doesn't have a lossless option, because it actually does and was added to the standard back in 1993. Most tools can't work with it, but nevertheless it does exist in the standard. The second is that PNG's don't have compression because they most certainly do. I can only conclude that you meant that in a different way. If you meant to say lossy, well, there are compressors that allow you to have lossy compression with PNG files, such as `pngquant`. There are others, but it seems to be the best at it as far as I'm concerned. If you meant something else I can't think of what.
2
I completely agree with this take, and as I said on your last video, they should've used an example repo instead of a production one, which you also said.
2
@momoanddudu Ah yes, the casual gaslighting of a state actor. Thanks for self identifying.
2
@momoanddudu Thank you for continuing to confirm that you're not a real human. And yes, companies do accept random blobs from employees to test, but you know that, you're just trolling.
2
@momoanddudu Your first statement doesn't connect to your second. Companies use binary test data all the time. Consider every single company that researches NN-based image recognition algorithms. They routinely use binary data for testing. If you can't understand that then I have doubts that you've ever worked for a company or done any programming work at all. Unless of course you already knew these things and are a state actor trying to gaslight.
2
Personally, when I first started programming and learned what a UUID was, I immediately said screw that garbage and never used them for anything. Need a key for a database? Use attributes of the data you're storing. Need to store secret data? Don't use a database to store it. Need to store less than 10 billion items and want fast access times? Use a hash table. In general, people use everything for the wrong purpose, and truthfully, B+-Trees aren't as efficient as they could be, nor are most tree structures when handling large amounts of data. I think a far better data structure, and one that has served me well, is a hash tree. It's an unholy mixture of a tree and hash table which allows for better distributed storage while yielding more array like speeds.
2
oblivikun On top of that, I'll say it again, end users should not need to care about X versus Wayland because the developers should just use a toolkit. In this case the toolkit has to care, and the WM or DE is the toolkit, but any program that you use which isn't a WM or DE shouldn't cause problems and the fact that they do shows a lack of capability on the part of the application developer.
2
@joshuathomasbird What would rereading your comment do for anyone? Are you not claiming that threading is not in the standard library? If you're not claiming that which is objectively wrong, then you may need to edit your comment.
2
I'm sure that 99% of developers will never get what I mean by this, but this is why you use toolkits. No one should care, or even need to care, about X or Wayland or low level primitives of the GPU, unless you're writing a game. A text editor, no matter how complex it is, shouldn't require this level of optimization, and if they weren't writing everything from scratch and doing the GPU acceleration by hand, they wouldn't have to worry about these issues. This has been, and will continue to be, my biggest complaint with regards to the rewrite everything crowd. Of course, if they were writing the toolkit, then this behavior could be overlooked because they'd need to deal with the complexity, but game developers have already solved these optimizations and if they knew anything about game development then they'd not be looking at it and going, "what is happening here". Maybe you think this is too harsh. After all, it has taken years of learning for me to understand everything that I do and they're probably in their 20's, but it goes along with what I've been saying over and over again about not reinventing the wheel. DRY code is better than WET code.
2
Those kinds of tools already exist for C anyway, both static and dynamic analysis. The paper makes the disingenuous argument that such tools aren't enough even though they're already better than what the Rust compiler provides and more feature complete.
2
How about a C compiler targeting WASM? 🤣
2
I think that maybe some people missed your overall point, which is a very valid point that applies no matter what language the project was written in or what language they want to move the project to. For my own perspective on this constant RIIR mentality, I've found nearly universally that when rewrites happen, features are lost. Even if the program runs faster, if it does less, as the user of that program I don't care if it's now viewed as a "safer" program. Of course, as anyone who knows more than one systems language can tell you, there's more than one way to skin a cat and Rust isn't any safer than other languages, even C. There are plenty of tools to do analysis of your code and keep your program error free that are far better than the Rust compiler and target languages like C. You can write high quality code in nearly any language, it's just a matter of skill. One could claim all they want that "Rust forces you to do things a certain way", but if you already write your code in that way then you shouldn't have problems with C, and if you don't already write your code that way then you were using C wrongly anyhow. If you didn't already know how to correctly write code, then you probably shouldn't have been a programmer in the first place, or you should just use JavaScript. As for the comments on async, I have always believed it's the wrong solution for the problem at hand. It's an attempt to merge the concept of a coroutine with threads and make them take less effort than threads, but it's still just threads with you having less control over what happens. True coroutines don't require separate threads, but the concept has been bastardized by everyone who keeps incorporating async garbage into languages. I look at them as being unnecessary work because it's better overall to just use the OOP method of saving state in memory somewhere, maybe even on the stack, and then just calling a function to update that state, which is more or less the generator concept. Consider that C already has that in its standard library with FILE's, where you can read some input or write some output and it's buffered. If you really want to read input in the background, then just use a separate thread, which even C has in its standard library now too. Although, I doubt anyone will read all of this, and it's most likely that someone will see this last line and comment that they read the whole post when they didn't.
2
I get why everyone thinks it's a valid argument to say that the formatter means no one has to argue over the format, but it's not actually valid. If you could keep your files in the format of your choice and when updating the repositories there would be a formatting phase that diff's the versions based on a minified version of the source and then others could reformat to suit their tastes on their end using a custom config, then it would make sense. Of course, that would require either an intermediate step where you copy all the source files to a second directory and then update the repository, or it would require a change to all versioning software. Since no one thought of either methodology, we're stuck here still bickering about formatting when we should just get on with our lives and write the code. All that said, the developers who maintain Go and all of the original creators can suck it hard because they've chosen to enforce a style that's garbage and have given an utterly braindead argument for why they have to enforce their rules. They're either lying or incompetent and in either case I don't want to use any software produced or maintained by such people.
2
@rlidwka I would say the only thing that can be done is to build out the infrastructure for such a system to work, maybe with a plugin to `git`, or maybe just editor bindings to automatically run a formatter on pushing and pulling commits and hope that the example set in using such a system gets copied by others. It would take a fairly deep analysis of how people actually style their code in each and every language which would require what is essentially a compiler for each language, so not at all an easy task. Languages like C and C++ would be easy since a large portion of what's needed already exists in various open source projects. As much as it pains me to say it, Go is practically done because of their unyielding design ethos and preexisting formatter. JavaScript has tons of formatting tools. Incrementally building the system out would be fine if the people pushing various languages contributed to such a project. Though, as far as I'm aware, there isn't currently an all-purpose code formatter.
2
I've been avoiding Go for a long while now because they chose to hardcode K&R style bracing, and public statements by the designers have proven they're either moroffs or evil in refusing to support an alternative. I get all of the not-see arguments for enforcing one style, but it's the entirely wrong approach. Last time I looked at TinyGo it couldn't do nearly anything, but if they've implemented their own compiler and would be willing to support Allman style bracing, then I might learn Go fully just for that. I'm not sure why you think that Scheme is some super difficult language. It's yet another LISP variant. If you want to play with it on your own time, I'd suggest downloading a copy of the Elk interpreter. It's a fairly well-written Scheme interpreter that can be embedded into other projects if you want to extend something, and it's written in an easy to read style. Fair warning, it is written in C.
2
In my experience, fresh out of university graduates are worth less than self-taught developers who spent the last 4 years teaching themself.
2
I think HTML, XML and tags in general were a mistake. He's right about one thing, self-closing tags with a superfluous space and slash are slower to parse, but we're talking about mere nanoseconds unless you have nothing but self-closing tags with superfluous slashes and spaces. In general 99.999999999% of tags will be wrapping tags, so a few nanoseconds are irrelevant. We'd be better off using an alternative format with less noise. Even something as simple as LaTeX would be better and even it has too much bloat, and is lacking a lot of things that the web needs. The best way forward would be for everyone to agree on a better format and collectively set out to use it, but since no one can agree we'll never move forward past these stupid years.
2
It's good that you came around to the correct way of thinking that this way of it working makes sense and that JavaScript sucks. Another example for you, consider a normal block in a language like C: int main ( void ) { int a = foo(); int b = bar(); { int c = a + b; } printf( "%d\n", c ); return 0; } // will not work because `c` had scope only within that inner block, but would if the printf() call was made inside that inner block. This is an overly simplistic example, but it demonstrates the point all the same that a variable can leave an inner scope.
1
Nope. There is no default formatting style with C. You choose what you want to do and the compiler doesn't care. You can even use Allman style bracing and it won't complain.
1
@thejeffkershner Back when I used it, I don't remember it having auto-formatting at all. I suppose it's possible I turned it off, because I hate that functionality, but then again, this was in the Win98 days.
1
If you've seen any of my rants on the modern internet, you'd already know why I think this is a stupid proposal. We should replace HTML/CSS/JS with a singular all-encompassing language. No more three separate filetypes that integrate in weird ways. We should use a single language designed for the web specifically. Something that makes it easier to define properties and operate on them. This proposal which would give us magic globals is really a bad idea. Something should only be visible between two functions if they pass a reference or it really is a proper global. The one thing I like about the proposal is no recursion, and if you've seen my rants on that you'd already know why. Although, in this case, to prevent recursion they'd have to introduce some sort of stack depth counter and disallow calling a higher function. Also, the result setting thing isn't equivalent with return, it's something that quite a few languages used to do which basically gave you a temporary variable that you could set and the end of the function equated to `return result` without you having to explicitly return it. Pascal and Object Pascal both had this functionality, as well as a few other languages. BASIC variants would often do the same thing by allowing you to set the function name to a value.
1
Good communication is key for a business to be a good business. Poor communication is a sign of a business being bad.
1
If you don't know what hot reloading is or why Rust is utterly incapable of the same in terms of iteration speed, then go look it up. Web servers on the other hand can be kept up once they're running and iteration is as simple as :w on the file you're editing then alt+tab to the browser window.
1
@Mordinel Not according to the documentation on their website. Says you have to use BufReader to get buffered IO.
1
@SlappyZA Cool, but why not ImageMagick?
1
I hope they don't yeet the io TLD because one of my favorite websites is Itch.
1
Yeah, because using the command line is super difficult. First you have to open a terminal app, then navigate to where the file is with `cd` commands, then type `convert foo.svg foo.png` and that's too much for fragile minds. Of course, modern file browsers can open a terminal at the current location if you check the right click menu, and then you only have to type that last bit, but nah, still too much for everyone who's not out of touch.
1
You graduated HS in 2013?! Damn, you make me feel so old. I do agree that Linux and Windows both have bad defaults, but I couldn't comment on Macs since I haven't used one since probably before you were born. However, I don't really agree with the complaint that poor defaults on Linux require each new install to take hours of setup. I've been carrying forward my config files for numerous pieces of software from as far back as when I used Win98. For instance, my ~/.vimrc has maybe had 4 or 5 lines added to it for each year since I started using Vim plus everything I initially put in there at that time. I don't have to spend more than 2 seconds configuring it for each computer it's installed on because I can just copy over the old config to the new computer. Most of my other configs really haven't changed by much at all in over 20 years.
1
@ArnoldsKtm A designation as a scripting language only pertains to how it runs. So unless the majority of users are compiling it to a native binary, it'll still be a scripting language. It's not a denigration to be labelled as such, it's merely what it is.
1
@theshermantanker7043 Using a buzzword doesn't magically stop it from being a buzzword. It's just part of the buzz spreading.
1
@theshermantanker7043 Since YouTube decided to shadow yet another innocuous post, I'll say it again. Multiple people using a buzzword doesn't make it not a buzzword.
1
I feel that way about certain characters too, and I've got a US keyboard. Here we call () parentheses or parens, {} braces and [] brackets. I prefer brackets for most things because I don't have to hit shift to type them, but I still use braces often in writing code because it just makes sense. However, I did toy with the idea of an all bracket version of LISP. It looked weird, but I think people could get used to it.
1
Many years ago before GH was a thing, SourceForge had way fewer ads. It wasn't until after GH rose up to replace it that SF started having far too many ads. Also, what the fuck is he talking about by saying that "open source" was coined in 1998? I don't know how old he is, but it was a term when I was a youngster back in the 80's. I had subscriptions to several magazines that had printed source code. GNU has existed since at least the 80's too. When I was in high school playing with Linux there were plenty of open source programs. Maybe not the millions that there are today, but thousands at the time is no chump change. Quite a few CVS servers had anonymous access, especially for open source projects. You rarely had to login or use guest credentials, and I tended to just not bother with projects that had such annoyances. Maybe I'm in the minority when it comes to reading changelogs, because I look at that information for nearly every repo that I play with. The `blame` feature of `git` is one of the most fun features that I use on a regular basis, too. I will admit that I like GH being user centric. Quite a few times I've pulled a user's entire set of repos just because they made it so easy to do. I've got a `bash` script which I can just give the user name to it, and it downloads their entire list of repos and yields a flat list of repo URL's. Then I can either just automate downloading all of them one after the other, or I can use `fzf` to select specific repos. One final note regarding Mercurial is that FireFox uses it. It's one of the more annoying aspects of building it because there's a whole complicated process to getting to code. They should have just moved to using Git at some point.
1
Every time I hear someone talking about Redis I have to look up what it is, then I think, "huh, okay", and move on. There are better solutions, and for most people they don't even need that much. Most projects I've done have been fine with a plain hash table implementation. I've done some crazy implementations of hash tables, but most of the time a straight up implementation works. The few times I've needed something as hefty as a proper DB, yeah, alternatives exist, and I could always just write something from scratch myself, if I needed to.
1
@keithjohnson6510 Maybe you're looking at the wrong thing, but the Watchman he references does indeed watch for file changes. A distinction for when the build system does anything is irrelevant unless you're saying that the project he was referencing that supposedly used Watchman didn't actually use Watchman. If that's the complaint, then you'll have to take it up with him.
1
@keithjohnson6510 He used it as an example. I criticized such a usage. If he was erroneous in it being used for the purpose stated in the video, then take it up with him.
1
@keithjohnson6510 Ah okay, so you aren't disputing his example, you're disputing my criticism of such a system. An unnecessary process hanging around in the background always eating up processor time and taking up unnecessary disk space just to tell you that there's a need to initiate the build system which still has to check the time stamps on all of the files anyway is wasteful. If the build system hooks into it to avoid checking every file, it's still wasteful, but also still ties into my criticism of such a program because it's not an onerous amount of work to check timestamps and it never has been, on any OS.
1
@RenderingUser Massively is debatable. It's the one modern language I adamantly refuse to use for a huge number of reasons.
1
@RenderingUser I'll just lump all of the decisions on forcing a particular design pattern and source code style into one giant complaint. Then add GC onto that list. You don't have to use low level memory handling to avoid GC either. Consider C++'s current memory management model as an example of more or less how to do it right. It's not perfect, but it's still better than everything that came before.
1
And here I am wishing that more apps would target native hardware. Is it too much to ask for a bytecode format that generates a native binary and gets cached and is specifically specified by a specification that specifies all of these details leaving no surprises? I would even accept a generic implementation as a VM for those platforms that don't have a native generator. Something like the JVM but without a single language attached to it, nor way of operating, and an intense focus on generating native binaries.
1
It seems like you dislike the idea of extending syntax and I feel like that might mean you would prefer how C++ does things over a language like Rust, at least if you were to learn a systems programming language. I'm not really a fan of either `?=` or `[foo, bar] = try ...;` but I also dislike exceptions in general. However, that said, for my own language I have been working on giving users the ability to select which type of error handling they like. I personally prefer a sort of hybrid of the Go method of collecting the error from the function, but I opted to allow the user to ignore it. Of course, it'll likely never see widespread use because people expect a programming language to wipe their ass these days, and mine lays the responsibility where it should be, the programmer.
1
@SnowDaemon ¿Por que no los dos?
1
Personally, I never found threads to be all that difficult and most of the time I was using pthreads for my threading purposes. Now that C11 added threads to the standard library and the implementation I'm using, gcc on Linux, basically just thinly wraps pthreads anyway and I have to add -lpthreads to the linker options if I use them. So I'm not sure why so many people complain about threading. However, I do wish that we could replace the entirety of the web infrastructure. Just completely wipe out HTML/CSS/JS and start from scratch. It'd be nice if bundlers weren't a thing and instead a webpage could just be simpler than they are now but provide similar functionality. Something akin to a web browser scripting a UI library instead of attempting to implement an entire OS inside of the already running OS.
1
If all of the Rustaceans are correct, then a breaking change wouldn't actually break anything because you set the target version number in your build file and it just works. Given that, they should all be willing to give it a try to write better code in a better way. But seeing the response from the cult in the comment section, I'm going to say they'd bungle it anyway.
1
Yeah, that's another one I don't get. My own language doesn't enforce a style on the users. Use whatever case you want, use whatever Unicode characters, even overload functions. So why every other new language has to do nonsense like that I don't get it.
1
@RenderingUser That's your opinion, and you're free to have it, just don't force it on others.
1
@Winnetou17 As far as hardware acceleration is concerned, I've got a computer that's only about 3 years old yet I have no acceleration for AV1 formats. Even playing video with Firefox it's basically a slideshow. And software adoption is pretty bad because I can only open such images with a browser. I've at least got 3 or 4 image viewers that can open WEB/P images, but not a single one knows what to do with AVIF.
1
@petrkdn8224 I can mostly agree with this, except bitmaps aren't obscure and while they're not common in the web space now, they were very common some years back in both the desktop and web spaces and are still used quite a bit in some places for their ease of generation.
1
I'm more than a little curious if JavaScript can be used to implement a custom floating point interpretation. I've partially implemented the operations in C, + - * /, and I can't imagine that it would even be possible in JavaScript without the ability to do a reinterpreting cast on the bit patterns. The thing I keep thinking about with all of these additions they keep coming up with is that we're going backwards in terms of functionality. We should be aiming to speed things up and all of these functional design patterns just slow us down and make the code more difficult to read. It feels like every advancement in computing power we've gotten has come with a devolvement in software which erases all of the advancement.
1
Why didn't you just use ImageMagick or InkScape or GIMP?
1
This isn't even in the top ten for bad code I've seen. I've trained a lot of newbies, and it was all in C. So trust me when I say I've seen crimes against nature first hand and barely lived to tell the tale.
1
As someone who predominately uses C for my work and fun, I was a bit confused at the term `signal` here as that word has a completely different meaning for me. As you went along I thought maybe it was actually message passing by another name, but this is quite frankly weird. It sounds like maybe it'll involve some sort of pointer with reference counting scheme, possibly some mutexes for locking and perhaps doing something similar to copy-on-write to check for changes in values. Although, I'm not sure how they'll be able to efficiently accomplish that because it would seem that it would require tracking changes at multiple points. Perhaps it's just because I've written my own compilers before and am currently writing one for my own language, but I'm curious as to how this will actually be implemented. It really sounds like an attempt to shoehorn in a common compiled language idiom for synchronization of data exchange but with extra steps. However, the most surprising thing about this video is you saying you don't know the word `elide`. I'll assume that was a brain fart because the article did misspell it in a few places.
1
I don't see how anyone could disagree. It really is what they do with JavaScript and every offshoot thereof.
1
It's bullshit like this why I still don't use GH, but especially the thought that it might change your licensing and absorb your codebase without your permission. That was a smooth move editing the article to promote your channel. And I feel called out for both using the word delve and starting sentences with `and`. I delve into different things all the time, and I've never had anyone complain about it, at least not to my face.
1
It's disgusting that our government isn't doing its job and filing antitrust suits on behalf of the people. Tim Sweeney is right that Apple and Google have monopolies, but even Epic still isn't doing things right. Their one saving grace is that they at least provide the technology to make games and it's great tech, but 18% is still too much. Any intermediary that charges more than 5% is just being a douchebag and greedy, regardless of what they think they provide. I might allow for Epic to double that because Unreal is a damn good engine, but definitely not 18%.
1
@SianaGearz The mistake was in not understanding how to handle it with words alone. The new mistake is to have a CoC. Such things are poison. Eventually you'll alienate everyone who you consider a them which leads to more problems than you can currently understand.
1
@SianaGearz In point of fact the person who was being referred to was not the contributor, but rather the potentially false identity of Jigar. The potentially false identity of Jia was actually kind to the original maintainer and sweet-talked their way into becoming the maintainer. How to deal with someone like him or her would be to say "no". As for an example of where a CoC makes a project worse, I'll let you search that out for yourself since you decided I "owe" you an example. Of course, we both know you wouldn't accept any example I could give you anyway. You come from a country that doesn't allow you your right to free speech and you clearly see nothing wrong with that.
1
Theo, the method that people should use should be dependent on how fast the codebase changes. Generally, 0.x.x is meant to be used until you reach a stable release, but I don't see that as being any more valid than reaching 10's of thousands of patches. The method I like is to use the date as the patch number, specifically with the international format. If you know the strftime() format specifiers then %F. If you need more than once per day releases, then I'd add _%T on to that. Once enough changes have accumulated, then bump minor. Once a breaking change occurs, bump major. Simple as that. Then the patch numbers are super easy to track, because it's literally the date of that patch, and major and minor pertain to public releases and API and feature changes.
1
Quite frankly, I just want one of those badges. If they've got plans for them up somewhere I'll have to find them.
1
As someone who likely spends too much time learning every new language that comes along, I can safely say that both Go and Rust are a mistake. However, if it was already working in Go, you're absolutely correct that it should've just stayed in Go. Rewriting a project in an entirely new language just because you like it is the easiest way to completely fuck up a project. I would argue that any new project these days should probably be written in a domain specific language, and if it's intended to run in a web browser the only choices are really just JavaScript and TypeScript and since TypeScript just compiles to JavaScript and is fully backwards compatible, it's not exactly different enough yet. If it's a backend application then the only real choice is C++. The reason being that it's a far better language than both Go and Rust combined and runs fast and compiles fast. Every time I use Rust I feel annoyed because it's basically a clone of C++ but with a shittier syntax and slower compile times because it aims to be more strict. Well, C++ compilers have all gotten better in nearly every way, and can enforce a lot of strictness on you while still compiling faster. Also, that part about not being able to interface between code generated with MingW and MSVC really hits hard. When interfacing different languages you have to compete with name mangling and a truly portable interface should be written for C compatibility, not just because you might just use C to interact with it, but because it doesn't mangle names.
1
This is pretty cool. Unfortunately, I've got a potato and it runs like a snail for me. Also unfortunate is that Nintendo will yeet it from the internet in 3... 2... 1...
1
I guess this explains why all the balls at the bottom had stripes, because I kept forcing priority requests to drop just for funsies. Going into the hundreds kind of breaks it, though.
1
@samrosewho You don't have to tell me, I already know I've got a potato. Cool interactive article though.
1
@momoanddudu Did you look at what they did in the exploit? I'm sure your bosses must have had you look at it to not make the same mistakes, but it was pretty sophisticated and nearly evaded detection. I'm sure the next version done by you or a co-worker will be harder to spot.
1
Unfortunately, we've already been going down this path for decades. A good historical marker would likely be the first circular reference on Wikipedia, but let's be honest, it's been happening since before Wikipedia even existed, it just provides the proof that it has happened. Print encyclopedias and journalists have done it since before the internet even existed. Basically, the corruption of the press is what has caused the slow but eventual downfall of humanity and few people see it. You should take a deep dive into circular references on Wikipedia and make a video on the subject.
1
Write a piece of code, compile, test, debug, write more, repeat.
1
@XCanG What word would you use?
1
Not predominately, but it is on occasion used for web development. There are transpilers that convert to JS as well as compilers to wasm.
1
@grail9558 There aren't many, but they do exist. Although, most, but not all, jobs that require C and revolve around the web space are generally about maintaining old code, generally stuff that only runs on the server or is itself the server software.
1
@casperes0912 I strongly disagree with this entire statement. There are already so many libraries, both open and closed source, that are written in C and C++, and I don't have to take time to write boilerplate code to get them to work, which are great implementations of algorithms regardless of any standard library, and that Rust doesn't by default provide. So much of the code that's gone into Rust was a rewrite of something that already existed in either C or C++, and often not a complete reimplementation. You can write good code in just about any language, but some make it harder and as ugly as C++ is, I can still make it cleaner than Rust by a wide margin. Even C can be cleaner with ease. And if you have to call a block of your code unsafe to get any real work done, then the language obviously doesn't provide real safety guarantees, nor is it complete. And if anyone wants to claim that only a tiny block of unsafe code in a known location means you know where the failure point will be, come back when you've grown up and worked on a larger project.
1
It's somewhat ironic that California would not allow non-competes when both the state and non-competes are essentially anti-capitalism. I agree with you regarding a free market, and non-competes are definitely bad. I also agree that the creation of more patents is bad, as they also denote a micro-monopoly on an invention which used to be required to be novel and non-obvious. All I have to say about modern patents is that the USPTO has horrifically dropped the ball these past 40 years and allowed many things to be patented which should not have been. I don't understand these RINO's that want to prevent competition. It should be a requirement that you are a proponent of free markets if you want to call yourself a Republican.
1
We're far beyond the times when a crash would lose all of your work. Now it's a logic error that results in accidentally deleting an entire database, and no language, not even Rust, will prevent that kind of bug. The only kinds of errors that Rust promises protection from aren't even particularly dangerous, nor as common as people keep claiming, nor do they cause as big of problems as people claim, and worse yet Rust doesn't even completely protect from them. You can even break through those barriers in pure Rust without using the "unsafe" keyword. If you were a serious developer who cared about safety, then you'd just learn how to actually program. It's incumbent upon you as the developer to provide safety for the users, not the programming language you're using. There are whole classes of errors that you can easily make in every language and if you expect that a language which promises saving you from two or three classes of errors to protect you from all the rest then please find a job in another industry.
1
@Sancarn A safe program can be written without exploding the line count. I would even argue that if you focus on safety first when writing your programs that you can minimize the effect it has on how your code looks. In fact, you can use macros to clean up all of the bookkeeping for whatever project you're working on. Obviously languages like C and C++ make such code cleaner looking, as in no need to type superfluous exclamation points to gouge someone's eyeballs with the fact that it's a macro. If you use C++ you can write your code in basically the same way as in Rust, but it'll look cleaner when using it, even if not as much while implementing it.
1
I can totally see that viewpoint. It's not as big of a win from other libraries, just different, and different slows adoption. One might make a similar case with React Query as compared to Ky, but then if you use React in the first place then you shouldn't be writing vanilla code anyhow and then Query should already be in your toolkit. Of course, in my field, this is one of the reasons why I get angry with junior developers who use C without ever once learning the libraries that make using it faster and easier. Instead I find them rewriting everything from scratch. Unless you genuinely have a better means of accomplishing the task at hand, writing it from scratch, which here would be equivalent to writing vanilla JavaScript, is a big no no.
1
I'll never agree that linter rules should be baked into a language, and I hate Go for doing so. I feel like all of these changes are an attempt to keep what should be a dead technology alive. The fact that TypeScript just compiles to JavaScript is especially annoying. It could be a good language if it had an actual standalone implementation, but it would need to shed the shackles of JavaScript. I know you'll never agree with me on this, and that's okay, but the world would legitimately be better off if HTML/CSS/JS didn't exist as a combination nor as individual pieces. We really need to replace all of our web technology with a single base language, and no, Wasm is not the answer.
1
Wow, 18px? You are blind. Maybe it's because I've always been told that "the web is not print" that I've always opted to not set a font size, but it feels nice to have my decisions validated.
1
@Bvngee The WM and DE are finishing the work of the toolkit. You can't just use Qt or GTK and then have no WM/DE, because there's more work that they do which neither Qt or GTK handle. And again, you shouldn't need to care how the toolkit is implemented at a basic level. It may double the workload for them to target two protocols and/or compositors, but that's the reason they exist in the first place, to solve the common problems so the majority don't need to worry about them. If they're making a user choose between X or Wayland, then they're doing it wrong. It's like the age old argument about just using assembly versus a higher level language. Or to phrase it in a catchy way: the problem is already solved, so stop trying to solve it.
1
From the context, it's clear he wasn't talking about refactoring but instead iterative development, and you can't deny that Rust is slower to compile than nearly every other modern compiled language. Even C++ compiles faster and it's a slow hog. Of course, if you don't have to compile and merely refresh the browser window, you have to admit that's going to be significantly faster still.
1
I would actually expect these results because it only has to fetch one file to process the page contents and start displaying things. However, I would also expect that a website that was developed properly would have some degree of backup mechanisms in place to allow for rendering to happen prior to the main stylesheet being fully loaded. What I am surprised by is the difference between inline styles and inline CSS with the style tag. That is where I would expect no difference, yet inline styles were faster, and while it wasn't expected I think I know why. Also, I would like to see a video on the whole rendering pipeline.
1
I don't understand how a theme can be copyrightable anyhow. It seems absolutely insane to me and I think our copyright laws need a vast amount of reforms to stop idiotic abuses like that guy attempted.
1
Okay, so the dude sounds like a douche, but you could've made this video 15 minutes and delivered all the relevant information. What you should be suggesting to him is to change careers. It doesn't appear as though development is a valid career path for him and he should consider becoming a burger flipper. It's a noble career path. People need food, and what better than the best type of food. Only reason this gets an upvote is because of the shirt changing joke. That genuinely made me laugh so hard I had to pause the video.
1
It's an utterly nonsensical default for a language to require you to configure the buffering that it does instead of defaulting to some standard good choice. I didn't even know that was its default behavior, but now that I do I'll add it to my list of reasons to hate Rust, so thanks.
1
@ReAnna__ It is a default because the sole in-language way of accessing files doesn't have a buffer. It is configuration because you have to account for it in your program very specifically with a separate interface. That adds overhead that shouldn't be there and isn't present in the basic interface in pretty much every other language. Since 99% of the time you're going to want to use buffering, that should be the default for the most basic interface. In my own standard library, I added an optional parameter to the File constructor that allows you to set a buffer size and make it unbuffered or even to finagle the amount of buffer. If the user doesn't specify, then it uses the platform default and is thusly buffered. Making it harder in the general case to satisfy the niche case is a bad move on a language designer's part. As for JavaScript and Go, they're bad examples of nearly everything. The fact that much of the standard library in Go isn't marked as @nogc even when a given function performs no allocations is extremely annoying. For reference, you can easily use a function marked @nogc from either side of that equation, but one which is not marked as such you can't use from an @nogc'd main(). For example, write*() functions. And no, telling the compiler to turn off all GC is not a valid alternative.
1
I'm pretty sure you don't read these comments, but I'll say it anyway. First, I don't know why you're reacting to a video that's just over a year old. Second, he's absolutely correct that JavaScript ruined the web, but not for most of the reasons cited. Yes, there are bloated frameworks and that's one of many problems, but the fact that many of the standards committees thought that JavaScript would fix deficiencies in HTML and CSS and thus never amended them to make them better is a huge problem. The fact that you can't just use a standard img tag and get good performance and instead have to use an alternate solution is a huge part of the problem there too. JavaScript is garbage and TypeScript which merely transpiles to it is also garbage. Neither language is any good at this point in time and should probably just be wiped off the face of the Earth, along with HTML and CSS. Now, for the statement on Linux, it's an operating system that requires more intelligence than your average JS developer, so if you can't merely upgrade to a new OS version, that's entirely on you. I've had no problems upgrading my OS many versions throughout the past 25+ years of using Linux. And yes, I mean without a full reinstall. That's not to say that you aren't allowed to do it that way if you want, or that when you're a new user you won't ever make such a mistake, but that at this late stage in the game, unless you're doing something really funky, you shouldn't have problems. I also want to specifically hit upon the argument for Electron. I completely disagree regarding dev time and effort when it comes to Electron versus desktop. If you're a more complete developer then you should have at least a modicum of experience in making a desktop app and there are numerous cross platform UI libraries that it should be easy to build a desktop app out. Hell, you could even use Win32 API and just run WINE on Linux, and we all know how many tools there are to generate code for Windows UI. However, wasting CPU cycles to use Electron instead of building a proper desktop app because you're lazy is a huge problem in the industry and far too prevalent of an attitude. I figured I'd add this in since no one will read it anyway, but the current version of Rust I have installed is 1.77 which I downloaded by cloning the repo and building. The entire folder takes up 19GB of disk space. Previous versions, before deleting them in full and starting from scratch because their build system is garbage, have gotten as high as 32GB. Every time I update it I wipe it out and start from scratch on building, which is fine because the binaries are in my home folder, so I can still build the latest version using the prior version, and from scratch always takes a full hour to build. So anyone who thinks that adding a requirement of the Rust runtime and build tools to a project is insane. It's a garbage language, like JavaScript, with a garbage build system, like JavaScript, and no one should use either language.
1
@fahimhussain1918 The size of a repo matters if you remember that more than one platform exists. There are people on more restrictive platforms than you or I and have no binary version of the software to use. Imagine wanting to use a modern and capable OS on older hardware as one of many instances. Linux keeps squashing old code lines so it's no longer viable for older hardware, and the requirement of having a Rust toolchain available for building it further squashes that thought. Then you have esoteric hardware that even if Linux still supports it, Rust most certainly will not. As for the false viewpoint that an open source and cross platform UI toolkit slows development down, you only have to consider the case where intelligence wins out and people learn how to do a UI using one of these toolkits instead of the platform dependent alternative. For instance, you don't need to target whatever Apple calls their UI, you could use Qt or GTK or any of half a dozen other toolkits. Pick one, stick with it, and you're done for all platforms.
1
Personally, I don't get why anyone needs all that junk in their editor. Are you a programmer, or a point and clicker? The only argument I hear that really seems to be in favor of it is speeding up development time, but if you don't know what is being done with all the code flashing on screen, then you're going to introduce bugs at some point which leak data or delete it or even just cause long outages, and when that happens, if you don't actually know what the code is doing then you won't know how to fix it. All of these auto features allow point and clickers to slip through the cracks and it's a very bad idea for the future.
1
Personally, I think wasm is a huge disappointment. I'd rather see Java make a resurgence as a browser language over ever using wasm. Although, we should have a runtime like Java built into the browser and having multiple languages should be no problem. We just need a VM that is more open for usage and not actually the JVM. In fact, if the web browser was just a glorified renderer for some VM-based language, we'd be far better off.
1
I still wish we could replace JavaScript/HTML/CSS as web technologies, and all in one go. And that bit about the W3C changing the spec because every browser but one was using a different ordering is truly sad. If no one codes to the spec then the spec doesn't actually exist and this is largely why I've hated web technologies for so long because almost no browser correctly adheres to it. The really sad thing here is that IE, of all browsers, was adhering to the spec in this particular instance and everyone else was doing it wrong. That's not to say that in this particular instance that they were wrong, but then I don't really think any of them were right, spec included.
1
You probably won't read this and YouTube probably won't send a notification anyway, and the post will likely be shadowed, but I'll tell you why I dislike this entire take. First of all, every argument for Rust is only valid if you're a new programmer and/or a bad programmer. The disingenuous argument that paper makes relating to "bug finding tools" applies even more so to Rust because the compiler doesn't catch nearly as many bugs as the static analysis tools for C, which are far more mature and feature complete, and there are exceedingly few dynamic analysis tools for Rust which mostly don't exist and would need to be written from scratch. The majority of dynamic analysis for Rust consists of bounds checking which slows the code down. You might say, "but you can turn it off", and then it's no better than C dynamically and there are C compilers which can add bounds checking anyway, but here's the kicker, that's a stupid feature anyway because the real problem with most code is the lack of proper user input checks. You can easily work with strings in C if you properly check user input, and using only numbers won't fix improper checks. Rust won't fix bad code, nor will it make a good programmer better. At best it'll force bad programmers to clean up their act. I know I'm yelling at clouds with this because the government is run by morons and it's going to happen whether I want my tax dollars wasted on it or not, and it won't matter in another decade or two when humanity destroys itself, but it still irks me.
1
Personally, I'd prefer if we got rid of all SPA's and reduce the shit out of the complexity of the internet. Get rid of HTML/CSS/JS entirely and reduce down to a single data focused programming language. If you want a proper application, use a proper application. What we generally refer to when we say "the internet" should not be the solution for every problem. It should not be the endpoint for every path. I know this falls on deaf ears, as pretty much every post I make on YouTube does, but everything is shit and it's because of the people that keep proposing this utter nonsense.
1
@joshuathomasbird What event loop? Do you think that the language gives you such a loop or are you merely stating the obvious that how you code your event loop, if you have one at all, determines how things will ultimately work?
1
I read the logs even for newer stuff, in fact, pretty much every repo I checkout, but I fully admit to being weird.
1
Personally, I like the increase in type inference. It can be difficult to implement, but I think it's worth it. As I've been working on my own language I've slowly been working towards anonymous structs being basically just another tuple type and that leads me towards arrays not needing a type at all as I'm already using brackets for both tupling and arraying. Eventually, I may end up using braces only for code blocks, and I kind of like the thought of that.
1
@oh3831 Learn it once and stuff it into a Bash script. You could even keep it on the desktop and drag and drop files.
1
You have an interesting perspective, but I think `let` was a mistake. If the default is mutability, then const needs to reverse that and we shouldn't have a keyword for mutability. Of course, towards that end, I think that JavaScript was a mistake. The lack of a reference or pointer designator was also a mistake. If you have a semi-immutable pointer type, such as the "humble" reference, then just use a character to denote it such as how C++ uses '&' or better languages use '@'. Then it's a simple matter of saying `const @foo = some_constant_garbage;` and then never changing `foo` at all. Also, it would make more sense if `const array = [foo, bar, baz];` meant that you could neither change what `array` points to nor the contents of the array it actually references. The const-ness of a particular object should propagate to everything contained therein.
1
@jcm2606 Quite a few languages got away with not using a keyword at all for declaring a variable and it was a simple matter of `name_i_pick = some_value;`. However, in my own language I went with a sort of hybrid single assignment method and using `var := whatever` works on initialization for declaring the variable `var`. Types then become zero or more of using the type name prepended before the first object in a comma separated list of objects or as the class constructor type, which works as a cast and type annotation.
1
I don't particularly care for ternaries, but if you're nesting them or your if/else's too much, then you're writing your code wrong. At some point, consider refactoring if you've got that much nesting, because undoubtedly it will be used in a loop and bog down your code.
1
I don't know how you could use a Mac after using Linux. I've been using KDE since almost its inception, and I couldn't use a different operating system and DE I've been so spoiled. I have 12 desktops set up and there are days when I use all 12. I have shortcuts for manual tiling because in general I just put everything at full screen unless I'm editing code and then it's anywhere from 1 to 4 instances of vim running to work on a project.
1
I think it's a huge mistake. JavaScript sucks and instead of keeping it alive they need to replace it.
1
@beedeeuniko I've seen far too many projects in the last 10 years that would contradict that assertion, unfortunately.
1
@jakelexington7610 Was that supposed to be directed at me, because I see no one else even using the word better. If it was, then you may need to reread what I wrote to come to actually understand it.
1
When you say chrome, do you mean the browser Chrome or the user interface decorations which the browser was named for? In either case, does this affect Firefox as well? Is this part of the standard for CSS or is it specific to the Chromium and/or Chrome source code? Regardless of whether you answer and/or how you answer, I'll keep saying that HTML/CSS/JS need to be wiped clean and a new standard needs to be devised for the internet.
1
@somenameidk5278 I guess you'd have to be into C to get it.
1
I was hoping this would be about a hardware device to route traffic on a network, but I guess a thing for managing projects to ensure links are kept up to date is cool too. Of course, things like this make it even more difficult to get devs to abandon all the old tech to wipe the slate clean and start fresh. If only we could fix the flaws in the current tech without wiping everything away.
1
It's weird how many people keep making the same invalid "points". It's almost like there's a cult of thought surrounding this programming language. Instead of teaching good programming habits, let's just push everyone towards the language that forces a narrow-minded viewpoint about everything. I'm not surprised though, since the majority of people involved in the project are all a bunch of tyrannical leftists. That same evil attitude of "there's only one way to do things, my way or death". This kind of thinking is why a certain group in the past rounded up people and sent them to really hard thinking camps where they baked a lot. The thing that apparently no one understand anymore, is that there is more than one way to do everything and while most of those ways are bad, there's still more than one that's good.
1
Yep, and now we're eating steamed jQuerys.
1
You're right, it's definitely a big deal, and I completely agree with all of your reasoning therein. The one point I disagree with you on is the bit about Google copying Java. I don't know if you remember, or if you're old enough to, although you should know of the project's existence anyway, but Sun, the original developer of Java, open sourced it back in the mid aughts. The project OpenJDK is the open source continuation of that code, pre-Oracle-buyout. Also, the case that Oracle brought regarding the use of their API, they did in fact lose that case. Granted, it did set a stupid precedent, that API's are copyrightable, but they rejected the claim that Google violated that. Modern Android basically just runs Java applets anyway, but the form has been heavily modified to optimize it, and the runtime is most definitely not the JVM. I'd love to see an open standard for computers, both mobile and desktop, where I could generate some bytecode and it really could run everywhere.
1
That level of fragmentation is nuts to me, but yet it happens so often. My suggestion is just to have a BDPP, a modification of BDFL to apply "per project" instead of "for life". Then that single person is the one to consult for all changes and no need to wait on a team.
1
@RustIsWinning Not really. It seems like more and more people are realizing that it's all a scam and moving back to languages like C and C++. Especially now that a corrupt government is recommending Rust.
1
I don't understand how there are still devs that don't know about ImageMagick. It has the ability to scale and all that other fancy junk, if you're willing to take 10 minutes to read a man page, and since you're a developer you should have no problem doing that, simple conversions are super easy by merely doing `convert foo.svg foo.png`. Let's say you want to batch convert, easy peasy, just do `mogrify -format png *.svg`.
1
I've probably been using Linux for as long as you've been alive, and for the first half of my time with it I used xterm and had minimal complaints. A long time back I switched over to using konsole and the only changes I made from stock configuration is to drop all of the window decoration nonsense and to change the default color scheme. I can use my mouse in vim, even scroll vim, less and man pages. Copying as pasting is easier and it's faster than my eyes can see. I don't understand why so many people complain about their terminals. Either they've not used konsole or they're doing something weird with different shells and blaming the terminal emulator for something it had nothing to do with.
1
I couldn't find your post responding to me, and I don't know if you or YouTube deleted it, but I'll point out here how ironic it is that so many proponents of open source are opponents of free speech while never stopping to reflect on the fact that they are the same thing. Software is speech and the descriptor of open with regards to software is the same as free as it relates to speech. If you can still see your post in your comment history, then YouTube is attempting to gaslight us both.
1
@blarghblargh It's possible, since they employ a lot of bad programmers at YouTube. Weird that it would impact you after so few comments yet me who tends to make controversial statements and gets a lot of dislikes have pretty much all of my comments visible, but like I said, bad programmers.
1
@blarghblargh This statement is unfortunately false as most say that it isn't free speech unless you also protect speech you dislike.
1
@blarghblargh It's not a legal right, it's an inherent right that the law merely codifies. There shouldn't be limits short of solicitation for criminal acts. Most on the right agree with that and most on the left used to agree with that, until they found it easier to control others if they limited speech more.
1