adamius
Same person can get a web job elsewhere with much less nonsense. So off they go.
Like a lot of things in IT these shortages are nonsense. They are lobbying for visa relaxation or similar so they can pay less.
Its an interesting field. But its seems not so easy to get the real methods used by the bigger models.
(I'm not using a supercomputer...)
Eg how do hou predict the temperature at x,y? Is it ground type, water, sand?Altitude? Neighboring values thereof?
What are the inputs? Do you give it a starting point and apply it to a bunch of elements like some giant automata like game of life?
Some kind of finite element analysis thing?
So many questions.
Upvotes and replies would serve as metrics on how well the AGI is progressing.
I'm not even sure you can accurately tell me all the uses for a 1 bit value let alone a kilobyte. The number of uses is independent of the number of combinations. If your answer is two you're way off.
Since when does knowing how many combination of states determine what you can do with something? Just because something has 256 states doesn't mean there are 256 different uses for it. There might be 124 uses for binary 00000000. But you won't know that by calculating 2^8.
There might be only three uses for 10100111. One of them makes the world feel pleasant, another melts your face off and another releases three male rabbits into the same cage. But I doubt there's only three. There's likely millions of potential uses for just that pattern alone. How exactly would you calculate how many? Accurately? I'm unconvinced.
The real issue here is lack of imagination. Placing limits where none need exist as well as failing to see possibilities without considering the vastness already present. 2^8 doesn't even begin to cover the number of uses for a single byte.
Rephrased differently: how many uses for a hammer? Can you know only by analysing its orientation? I doubt it.
Rephrased differently (again): feeding a particular combination into different machines will generate a different result. Can you predict the number of results from a given combination without knowing how many machines could process it? I doubt it. The question itself has too many unknowns in it.
The codebases we work on are from the 1980s. They sorely need to be dragged kicking and screaming if necessary to later standards. So many warts. People abused the preprocessor like it was normal and expected.
The semantic change isn’t as big as you'd expect. Even as it is in fact a semantic change. But I sense significant gatekeeping as well to hold back the tide.
Its just a code smell. There are likely other bugs hiding around the code. Business logic issues as well. Overall its a story of generally poorly written and ambiguous code. So... Perhaps fix it?
If you can't fix it then a compiler option would do it.
Deprecate this requirement already and make it an option. Gcc --stupid-typedef-required
Edit: or stated in another way, please describe the good reason(s) for having typedef struct {} Foo in C. Do it in terms of justifying the extra typing / extra steps. I'd really like to know. This is extra code and one more thing to test and confirm. Don't reference history or "its just how its always been done" - that to me is an admisson that it needs to go into an option. Also you'll need to explain why its bad that C++ doesn't require this. I'd also like to see as part of this rebuttal a formal statement that C++ got it completely wrong.
So: Why in C do we require the extra steps just so we can get rid of the struct keyword having to be plastered everywhere?
Personally I think the typedef struct pattern is kept purely for historical reasons and is no longer necessary. It obscures the code rather than clarifies it. There are much better reasons for using typedef but getting rid of "struct" prefixes everywhere isn’t one of them.
Are the hours you are putting in like a sprint or a marathon? Is this sustainable?
Oddly enough, though, all those things you listed are possible if you reduce the scope and scale of the projects. Its a matter of saying no to massive undertakings and be pragmatic about it.
A "programming language" doesn't have to compete with C or rust or something equally huge. It could be a little DSL instead. "Cryptography" could be a key store or other simple encryption tool. The "sci-fi epic" could be a novella or even a short story.
But at the same time, even those undertakings might still be too large a bite to take out of your weeks.
So, as you say, prioritise and accept your own limitations.
how many killings would this kind of check have prevented in the past?
What does the data say?
The trick is to weight them correctly. Multiply positive by 5. Then re-evaluate. It helps. Negative people find water disgusting and yet water is a necessity for life. Its therefore very important to keep perspective.
That's the pragmatic explanation I use.
Otherwise, and especially if you think servers are somehow always somewhere out there, you'll get a rude counter example. Server just means provider of service and thats about it. You're tripping up on your own assumption.
This is why you can telnet/ssh to a server out there, set the display variable to point back to your machine and xterm will try and connect to your machine. Its wanting a connection to your display to show things and to do so it needs a display server, ie yours.
That all probably made sense.
The big sneeze involved some fancy face decorations as well. These things aren't cheap either.
Then again, whats a TB worth on just one xeon server? Probably cheaper... or not?
As for gcc, I'm fairly sure gcc has at least one out-of-tree but yeah perhaps the code wasn't as good as hand rolled.
This is how I stay on target and finish things. Perfection is only a justifying set of sweet lies that prevent finishing.