![]() Some use bloated to mean the memory footprint. The same could likely be said for GTK in reverse, I'm not sure what their relative sizes for similar features are these days. The very root of the GNU toolchain, Herd etc are probably there.ĮDIT: Typos + corporate software development environment.įrom a user perspective I remember that being a big thing some time ago when people didn't have anything already using Qt installed did an “apt install” or “yum install” on something that did and saw the small tool they were wanting was going to drag half a desktop environment in with it as dependencies. It started that way, it is about hippies and naysayers. Open source is all about anti status quo. Happens to all of us and if not, wait for it.ĭeclaring a single boolean flag in a corporate environment might cost more then an hour to get to a consensus because one I-am-dffierent-I-care-too-much guy has some objection about some ambiguity in the flag name in some far future and has now swayed roughly half the team on his side. You two might like different pigments for the grass and he'll strike down your painting with a red ballpoint if not to his taste. Many are just complaining to make sure they're considered the quality sensitive cooperate loyals. It has moved and distributed the part of the factory shift in charge to the dude sitting next to you, cleverly. You like it, then you like it, end of the story, you're not playing for the gallery.Ĭorporate enslavement works differently. You don't get your paintings code reviewed. Software developed in the wild does not have those corporate obligations and the sole purpose is to enjoy the process, the sheer joy of creating something. Much of our professional habits are part of the corporate chains which is optimised to deliver and squeeze as much as possible. Now I'm ready for massive downvotes here but hear me out. it just took a long time, and I became increasingly terrified of making changes. I'm a huge proponent of automated testing, and I wrote a relatively large, cross-platform renderer without a single automated test back in the late 90s/early 00s. No-one worth discussing the issue with claims that it's impossible to write complex code without automated testing. I figure the author probably does test their code (everybody tests, even if that just means running the app), but not rigorously or in a way that you could say gives one the security of regression tests. What they're saying is not that you don't need testing or code reviews, but that you can get your users to test for you. > If many people use your app and it crashes, they’ll tell you and then you’ll fix it. > If no one uses your app then who cares if it crashes. > I do know that you can write complex, relatively bug free code without anyone looking over your code, because I did it. And yet I do know that you can write complex, relatively bug free code without tests, because I did it. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |