|
JawnV6 posted:it can't really? things that are "fine" but probably aren't what the author intended are the whole point of warnings
|
|
|
|
|
| # ¿ Jan 22, 2026 04:38 |
|
they're basically unavoidable. even ye olde cgi web sites are a simple distributed system. just imagine that all of your various services that need to talk to each other are impatient users mashing the Submit Reply button over and over
|
|
|
|
react native’s killer feature is hot reload, which lets you modify your app while it’s running and have it update instantly this is very important when using a framework that basically only supports programming by trial and error and loving around until things appear to work
|
|
|
|
gonadic io posted:since when has that stopped anybody i learned c++ in my (public) high school’s AP CS class 15 years ago, and it was not a newly added class then. CS was far from the bottom of the most-taken AP testa the year I took it, too in uni there were some people who had never programmed before but they were the minority and most people bitched about how weird and different scheme was from what they were used to
|
|
|
|
cinci zoo sniper posted:what’s the proportion of swift shops vs whatever is the react native of current year 100% of the shops you actually want to work at are swift shops there’s basically two categories of companies that use react native/xamarin/etc: 1. fad chasing fart huffers 2. companies with zero budget for the app who are looking for the cheapest option regardless of quality
|
|
|
|
DONT THREAD ON ME posted:eschaton there is no reasonable way to get vim-mode in my xcode. i hold you personally responsible, as an emacs fan you should appreciate the importance of extensibility. https://github.com/xvimproject/xvim2 works vaguely okay except for all the things that don't work. just don't look too closely at how it's implemented because extending an editor that doesn't have any official support for plugins is pretty yikes.
|
|
|
|
the attack vector that it opens is that if someone steals your private key, they can trick you into loading their code into xcode's process. even that can be prevented by just deleting the private key used immediately after signing xcode + xvim with it.
|
|
|
|
obviously don't download one of those "convenient" pre-built xcode+xvim packages because that's how you get ownedd
|
|
|
|
today i wrote a test which launches three different database servers and called it a unit test
|
|
|
|
the divisions in types of tests that i have found useful are things like: 1. fast tests vs slow tests 2. deterministic tests vs flaky tests that are expected to fail sometimes 3. tests which are self-contained or set up everything they need vs tests which require me to spin up some external thing 4. tests which i can run while doing other things on my machine vs tests which have to be run on a second machine 5. tests which make it easy to tell what actually went wrong vs tests that just go "lol you have a bug somewhere" now, there's certainly some correlation between these properties and the traditional unit/integration/system tests division, but it's not like a test suite consisting entirely of pure authentic unit tests can't be painfully slow (even if it's harder) and integration tests can be fast. unit tests tend to make it easy to tell where things went wrong, but a good integration test is built out of pieces that themselves have tests and is only uniquely testing one specific thing, so if only that test fails you know it's that thing. basically i think "is this test actually a unit test?" is an okay question to ask when you're getting started with writing tests, but doing things like writing mocks purely for the sake of making something be a unit test is not an inherently useful thing to do. write mocks because it's too hard to write the test without mocks or using the real thing is too slow or makes your test unreliable or hard to debug, not just for the sake of writing mocks.
|
|
|
|
Beamed posted:
did you completely miss that 10 year period where everyone loved dynamic typing and thought that static types were just a legacy thing that used to be required for good performance?
|
|
|
|
step one is quit your job and live off savings for a while
|
|
|
|
air fryers are a sandwich
|
|
|
|
use machine learning and train an agent on a large corpus of code in your language and non-code comments
|
|
|
|
CRIP EATIN BREAD posted:also about comment parse chat: merely finding comments is the easy part. c++'s grammar may be a mess but it's not that much of a mess. the hard part is then deciding if a comment is allowed or not
|
|
|
|
DONT THREAD ON ME posted:some people take hungarian notation way too far i miss that coc poster who would argue for advanced hungarian where you encoded a whole bunch of things about how a variable was used in the name and then skip actually giving it a name because that’d be superfluous
|
|
|
|
Brain Candy posted:also lmao that windows doesn't have a good epoll in TYOL 2019 iocp is awkwardly different from epoll in ways that make porting code written for epoll to it hard, but it isn't really inherently worse.
|
|
|
|
Space Whale posted:We make stuff that tells a pilot what settings to use, if the airplane is too heavy, if it's too hot for your altitude and weight, and engine out procedures, mostly. Also balance poo poo. these sound like things that could result in a crashed plane if you gently caress up enough
|
|
|
|
animist posted:lets put socialism... on the blockchain!!!1 that's bittorrent
|
|
|
|
it was sorta mindblowing the first time i worked on a system where the network was faster than the disk
|
|
|
|
raminasi posted:that compensation is possibly appropriate for an entry-level job at a rural non-profit but nowhere else 30k is literally minimum wage here for a computer toucher position it's an appropriate rate for a high school student summer job where there's a good chance that they'll do literally zero work
|
|
|
|
yes wcf is the replacement for .net remoting and it’s worth making the transition
|
|
|
|
ulmont posted:That's probably covered by the Confidentiality and Invention Assignment Agreement, to be perfectly honest. yeah, those usually have some sentences saying you agree to dispose of any company ip you have when you leave
|
|
|
|
crazypenguin posted:ah, yeah stroustrup brings it up a lot when talking about c++ template/concept syntax. originally c++ didn't have the template<typename T> boilerplate but it was added because people were worried that it wouldn't be obvious that a function was a template and that'd be a big problem for some reason. no language since which has generic syntax inspired by c++ has included similar boilerplate and it's never been an issue, and now that templates aren't a new exotic thing everyone wishes we could get rid of the boilerplate.
|
|
|
|
most languages manage to make due with void foo<T>(T arg) rather than template<typename T> void foo(T arg); and c++ could have as well
|
|
|
|
NihilCredo posted:there are only two kinds of languages: the ones people complain about, the ones nobody uses, and sql i want to live in a world where people just use sql rather than complaining endlessly about it and building impossibly awful things just to avoid having to learn sql
|
|
|
|
TheFluff posted:it really is, but people just don't seem to get it for some reason. i saw some dumbass complaining on twitter the other day that they were disappointed there was no ~innovation~ in database query languages so here we are with 1970's sql, ugh it's also just plain wrong in that modern relational databases support a hell of a lot beyond the core relational algebra stuff that sql started with
|
|
|
|
there's a shitload of room for a better sql that fixes all the minor annoyances in sql and results in overall a much more pleasant experience for people who use sql, as while they're minor individually there's so many of them that they really do add up i just agree with the notion that those annoyances aren't why the people who refuse to just learn sql aren't using it.
|
|
|
|
CRIP EATIN BREAD posted:that looks like pretty standard stream handling in any language doing the same thing with xmlhttprequest is like 3 lines of code fetch makes simple cases easier and everything else way harder for no good reason
|
|
|
|
CRIP EATIN BREAD posted:yeah but you get flexibility then. all you need to do is just write your own utility to wrap all that for you and boom, it works just like before. what if i told you that it's possible to make a flexible api without making common basic use-cases garbage
|
|
|
|
CRIP EATIN BREAD posted:there's no good API written in javascript so you're not losing anything on that front. the thing which that pile of garbage for fetch() is replacing is the following: xhr.onprogress = (e) => console.log(`${e.loaded / e.total * 100.0}% done`) xmlhttprequest on the whole is not great but that's a pretty reasonable and good way to expose download progress. forcing you to implement a general-purpose stream transformer just to get progress information is not.
|
|
|
|
CRIP EATIN BREAD posted:but i mean, you implement a wrapper once, that does the work for you, and you can use it. or instead of making literally every person who ever uses a lovely api have to write a wrapper to make it vaguely acceptable, you could just make an api that isn't poo poo to begin with
|
|
|
|
Blinkz0rz posted:errors as values isn't that weird though errors as values doesn’t inherently introduce a duck ton of boilerplate errors as values in a language that doesn’t do anything to make errors as values work well and doesn’t let you build your own abstractions is what does
|
|
|
|
gonadic io posted:Locale sensitive string comparison is like crypto, or datetimes. Just refuse to touch the implementation code 100% of the time and leave it to weird genius loners. You will never ever get it right. and much like with crypto, even if you just call someone's else's code that does everything for you you're still probably going to call it incorrectly because there's some irreducible complexity
|
|
|
|
the really amazing thing about git submodules is that the tools actually have gotten quite a bit better over the years it's just that the starting point was that you had to hand-edit the files in the .git directory for a bunch of operations and even completly trivial and routine things would leave your local state totally hosed
|
|
|
|
gonadic io posted:i'm going to go with yes because it's not written in loving js it basically would be if it supported vscode’s plugin api.
|
|
|
|
eschaton posted:Xcode will index code without building it, the indexers are based on the compilers so they’re fully accurate xcode will also use a cpu core on the separate indexer process while building to make sure that your builds take long enough
|
|
|
|
open offices are acceptable on days where i'm the only person in the office one or two other people working quietly would be acceptable as well except for that inevitably one of them will loudly proclaim "boy it's quiet in here!" and make me hate them
|
|
|
|
DELETE CASCADE posted:most of those data structures are made up of pointers whose addresses will definitely not be valid anymore if you restart the program just turn off aslr and every other security feature from the last 30 years
|
|
|
|
|
| # ¿ Jan 22, 2026 04:38 |
|
gradle is fine if you don't mind a build too that takes a minute just to decide what to build every time
|
|
|




