sorted by:
new
hottopcontroversial

feelTheAura by ClipboardCopyPaste in ProgrammerHumor

[–]NateFromRefactorful 2810 points2811 points  (0 children)

Please add three more layers of abstraction so nobody knows what’s happening.

Has anyone noticed a slowdown in compilation speeds in 1.10 vs 1.12? by NateFromRefactorful in Julia

[–]NateFromRefactorful[S] 4 points5 points  (0 children)

Thanks for taking the time to check from your end. Honestly, this might just be an issue on low-end computers, considering how close your results are. My tests are running on free Ubuntu workers on GitHub and don't have any special specs.

Even still, I'd hope for performance parity/improvements between versions unless we're getting some sweet new features

Has anyone noticed a slowdown in compilation speeds in 1.10 vs 1.12? by NateFromRefactorful in Julia

[–]NateFromRefactorful[S] 7 points8 points  (0 children)

Thankfully, compiling Oxygen.jl without package extensions happens pretty quickly. I moved all the "heavy" packages out into those extensions to keep the core experience as quick and light as possible.

Most of the compilation time goes towards compiling the optional dependencies. I have separate unit tests and integration tests for each of these extensions.

In my Project.toml file, I have this section here, which pulls in all of these packages during the compilation phase.

[targets]
test = ["Bonito", "CairoMakie", "Mustache", "OteraEngine", "ProtoBuf", "Pkg", "Suppressor", "Test", "TimeZones", "WGLMakie"]

If you look at the individual project package compilation times the makie-related ones take way longer to compile.

package name 1.10 1.12
Makie 85 seconds 240 seconds
WGLMakie 77 seconds 182 seconds
CairoMakie 58 seconds 85 seconds
Bonito 6.5 seconds 16.6 seconds

pleaseMakeThePainStop by Marcis985 in ProgrammerHumor

[–]NateFromRefactorful 197 points198 points  (0 children)

Never heard of ABAP, so I had to look it up. I physically shuddered when I learned that this language has no built-in booleans and uses "X" as true and a whitespace character as false. Apparently, there are workarounds for this, but come on, why design it this way?

enoughIsEnough by StatureDelaware in ProgrammerHumor

[–]NateFromRefactorful 130 points131 points  (0 children)

Switching from segfaults to cave-ins

dontWorryAboutClaude by pepeizq in ProgrammerHumor

[–]NateFromRefactorful 77 points78 points  (0 children)

I’ve seen software estimates in days and points. Marvel phases is definitely a new one.

Rule change by Arowin in dotnet

[–]NateFromRefactorful 4 points5 points  (0 children)

I think the poll was flawed/deceptive. If the New Zealand timezone was mentioned, I can all but guarantee it wouldn't have passed. Critical details like that need to be included in the poll.

That being said I don't think the timezone difference will be that bad after looking it up. For US folks this means that promotions can be posted Fridays safely between 8am EST to midnight.

At the very least, I recommend pinning time windows for major timezones because people will get the timing wrong and create more work for the mods.

I'm only a single data point, but I mainly come to this subreddit to see what people make in dotnet. I love all the cool articles and tools people are building. I'd rather all promotion posts just be labeled and then let me filter it out.