:(

Well they should at least provide a trace id or something that can be handed off to support team or dev if it keeps happening. The reason behind the vagueness of the error message is probably because its either the default for unhandled errors or they dont want you to know the details since it might reveal things the company would rather others not know such as their stack and whatnot

@TrevorTheRat i mean sometimes, but the time spent moving data across the network is always the determining factor unless your app server code is atrociously slow. So if moving more processing onto the database side significantly reduces the amount of data transmitted over the network, then that would probably be faster albeit less easily maintainable. But even then it would be faster primarily because less data is travelling over the network.

I remember a few years ago i was implementing velocity controls at one point and made use of stored procedures because otherwise every request would be fetching a bunch of records only to reduce them to a summary statistic on the app side. I didnt benchmark the two possible approaches at the time since it seemed obvious to me which would win.

@RememberMe Im familiar with Monad but was trying to understand Arrow and how i might go about implementing something like that in typescript for like... learning purposes. Came across the academic paper that introduced the abstraction and well.....

I think it was this one
https://doi.org/10.1016%2FS0167-642...

I feel that, i read about Arrow(s) as opposed to Monad(s)... reread it a few times, still didnt quite "get it". I mean the basics of FP are simple but some of the FP abstractions get super academic and reasearchy. All haskell, math, and in an academic paper

And then you have OOP where, its problems aside, explanations of the design patterns are readily available and easy to understand.

@theabbie im the other way around. A server side focused dev who sometimes has to write frontend code/html/css as well as provision/ maintain cloud resources. I can get by on the frontend but its a much slower process for me than for someone more highly skilled on the frontend.

I agree though with the general sentiment that its hard and unusual for someone to be highly skilled in UI/UX design and implementation as well as the more logic focused backend work.

But honestly, a good dev should be able to shift gears and adapt to whats needed. A good javascript dev on the frontend is still a good dev and can learn the backend if needed. Likewise a good backend developer can get by on the frontend as long as everything looking like everybody else's work is ok (i.e. bootstrap all the things).

It just takes time and experience

Functional and OOP styles/methodologies can be mixed and matched within a codebase without a problem. Use what works well and looks nice for a particular bit of functionality in code.

I guess we are in the middle of a renaissance in functional programming, partly driven by it being arguably better suited for data processing by cleanly representing it as a series of data transformations encoded as functions (BigData, ML), partly because the statefulness embraced by OOP makes behavior less predictable at a glance

All this runs against what was commonly taught and evangelized: that OOP is a one-size-fits-all paradigm superior to what came before it.

There's another use for CORS that hasnt been mentioned yet: preventing people from using certain apis from the browser. Imagine for a second that somebody decided to send a payment request for a product to their payment processor from the browser. If allowed to somebody somewhere will do that very thing. FYI the only remotely semi-secure way to do that is if the endpoint is authenticated via a one time use token of some sort. But even then its plausibly manipulatable by tweaking things to block the api call to the payment processor and then using the token that call would have used to authenticate with a goddamn payment gateway.

Annotations are honestly one of my favorite features of java.

Whether its for code generation by tagging something for a code preprocessor (lombok), or adding metadata to tell a framework/library how you want it to work (spring DI, spring rest controller, jpa, etc), annotations make this easy by being concise and declarative

Or just... you know, mention that some meetings you dont seem to be needed on and time could be better spent elsewhere. If by not needed you mean standups then no you are probably stuck with it.

I heard about that happening at my company, not sure on the details but i dont think anyone was fired, granted it was less than $20 but i think it actually charged an it manager's account rather than a proper test account. Im pretty sure they just refunded the charges in that case and all was well

So i found an article on this but it looks like its actually about official support rather than a hard restriction so i was wrong

https://theverge.com/2021/6/...

Looking elsewhere it looks like the breaking hard requirement changes are more around:
- requiring 64 bit processors
- hardware level security via TPM
- requiring more ram (not good)

Back to the question around CPU features, its more about instruction sets.

When a new intel processor is released it could hypothetically have a new supported instruction that when used speeds up particular computations. But to make use of that instruction your binaries themselves need to reference it, which means those same binaries cant be executed by processors lacking that instruction.

Thats my understanding of it anyway

I heard theyre targeting only newer cpus, which would allow them to presumably simplify their kernel a bit compared to the wider support seen in 10.

Would it make windows 11 faster? Depends on if they werent already bundling redundant binaries to account for optimizations available in newer cpus but not older ones.

Would it make windows 11 smaller? Depends on the above and whether savings on one side of the OS are being used to justify filling up that space some other way.

Does it require a 10->11 change?
Yeah unless windows wants to brick a large number of devices post update.

Will it make their hardware partners happy? Definitely.

@iiii perl's a nice flexible language.

used it for a couple years straight modernizing old perl server code.

But damn there were some serious performance issues with popular libraries like "moose" which greatly expands oop capabilities in perl. Had to settle for "moo" or something like that because the startup time with moose was java spring level awful and it wasnt even doing dependency injection

Once you're no longer a contractor and are officially hired, things SHOULD improve, but probably not by much.

Id look at other options if i were in your shoes.

What youve gotten thus far sounds like busywork which might be because they dont want to give the important stuff to someone who might not stick around.

But the lack of awareness of who you are and why you are there suggests a total disconnect from the team which doesnt sound like a company/team interested in gaining, evaluating, and keeping good developers, but rather one comfortable with keeping the team the same size.

Knowing apple they probably did just want it to be harder to port.

I have two choices:
- windows: plenty of technicians can support so no admin
- mac: 1 support technician so admin for me

Its an easy choice

Then just use kotlin + spring boot if you dont like java's verbosity

And like mentioned elsewhere, lombok is your friend in java.

But really, its not that bad, spring provides so many features and has sensible defaults in most cases. The only thing id complain about is the startup time of jvm+spring.

Sure java is more explicit and has fewer shorthands than some languages but spring is probably the best framework ive ever seen for any language.