Hacker Newsnew | past | comments | ask | show | jobs | submit | cardanome's commentslogin

The easiest solution is to simply self host your fonts.

The easiest solution is to use the default font. This has the additional benefit of being the most legible font for every reader, because it's the one they have the most experience reading.

remember the times when common sense was to not accept the remote site's fonts, and thus web devs should not use them

Yes. I recommend everybody to do a deep dive into font file formats and you'll see a lot of monsters hiding.

That definitely deserves better tooling!

The paycheck?

The vast majority of software projects fail. Honestly, I can't remember ever in my career working on a project I really believed in.

Sometimes I do enjoy the challenge of doing the impossible. Turning a doomed project around or at least minimizing damage. I had some where I thought "this worked out but if anyone but me had been in charge, yeah this would have been a disaster". That feeds my ego. Though I never ever get any thanks from management or any praise. Though this is more of a German culture thing.

There is a reason why burn out is so high in software dev. You are set up to constantly fail. If you succeed against all odds you get more and harder work until you fail.

You got to focus on yourself and find joy in the little challenges. Don't fret over things that you can't change.


That's insane. I think about 80%+ of the projects I see attempted succeed in at least some limited fashion. Even the failures in retrospect produced some insight into the right way forward and were necessary as part of research.

That’s crazy sauce. I don’t lose.

The one time a project was heading to failure I went to the VP and explained the sabotage I was seeing. This was a very lucrative contract and failure was not an option.

He pulled that manager and his team so far off they had a new office on the moon. They were pulling non-sense like submitting the pseudo code I white boarded as a commit.

Two weeks in and I’m still explaining to them the plan.

Despite the setback I pulled off a mammoth project and strategically moved in devs to areas where they could succeed. If they slowed me down they were given the boot.

Success sometimes just takes drive.


For release builds yes. For debug builds slow compile times kill productivity.

If you are not willing to make this trade then how much of a priority was run-time performance, really?

It's never the case that only one thing is important.

In the extreme, you surely wouldn't accept a 1 day or even 1 week build time for example? It seems like that could be possible and not hypothetical for a 1 week build since a system could fuzz over candidate compilation, and run load tests and do PGO and deliver something better. But even if runtime performance was so important that you had such a system, it's obvious you wouldn't ever have developer cycles that take a week to compile.

Build time also even does matter for release: if you have a critical bug in production and need to ship the fix, a 1 hour build time can still lose you a lot here. Release build time doesn't matter until it does.


A lot of C++ devs advocate for simple replacements for the STL that do not rely too much on zero-cost abstractions. That way you can have small binaries, fast compiles, and make a fast-debug kinda build where you only turn on a few optimizations.

That way you can get most of the speed of the Release version, with a fairly good chance of getting usable debug info.

A huge issue with C++ debug builds is the resulting executables are unusably slow, because the zero-cost abstractions are not zero cost in debug builds.


Unless one uses VC++, which can debug release builds.

Similar capabilities could be made available in other compilers.


Its not just the compiler - MSVC like all others has a tendency to mangle code in release builds to such an extent that the debug info is next to useless (which to be fair is what I asked it to do, not that I fault it).

Now to hate a bit on MSVC - its Edit & Continue functionality makes debug builds unbearably slow, but at least it doesn't work, so my first thing is to turn that thing off.


Which is why recent versions have dynamic debugging mode.

You can debug release builds with gcc/clang just fine. They don't generate debug information by default, but you can always request it ("-O3 -g" is a perfectly fine combination of flags).

Not really, because some optimizations get the step through and such rather confusing.

VC++ dynamic debugging pretends the code motion, inlining and similar optimizations aren't there and maps back to the original code as written.

Unless this has been improved for gdb,lldb.


Ah, I see what you mean.

GCC can now emit information that can be used to reconstruct the frame pointers for inlined functions: https://lwn.net/Articles/940686/ It's now filtering through various projects: https://sourceware.org/binutils/wiki/sframe

It will not undo _all_ the transformations, but it will help a lot. I used it for backtraces, and it fixed the missing frame issues for me.

This was possible with the earlier DWARF format (it's Turing-complete), and I think this is how VCC does it. Although I have not checked it.


I think this also massively depends on your domain, familiarity with the code base and style of programming.

I've changed my approach significantly over time on how I debug (probably in part due to Rusts slower compile times), and usually get away with 2-3 compiles to fix a bug, but spend more time reasoning about the code.


Doesn’t rust have incremental builds to speed up debug compilation? How slow are we talking here?

Rust does have incremental rebuilds, yes.

Folks have worked tirelessly to improve the speed of the Rust compiler, and it's gotten significantly faster over time. However, there are also language-level reasons why it can take longer to compile than other languages, though the initial guess of "because of the safety checks" is not one of them, those are quite fast.

> How slow are we talking here?

It really depends on a large number of factors. I think saying "roughly like C++" isn't totally unfair, though again, it really depends.


My initial guess would be "because of the zero-cost abstractions", since I read "zero-cost" as "zero runtime cost" which implies shifting cost from runtime to compile time—as would happen with eg generics or any sort of global properties.

(Uh oh, there's an em-dash, I must be an AI. I don't think I am, but that's what an AI would think.)


I used em dashes before AI, and won't stop now :)

That's sort of part of it, but it's also specific language design choices that if they were decided differently, might make things faster.


People do have cold Rust compiles that can push up into measured in hours. Large crates often take design choices that are more compile time friendly shape.

Note that C++ also has almost as large problem with compile times with large build fanouts including on templates, and it's not always realistic for incremental builds to solve either especially time burnt on linking, e.g. I believe Chromium development often uses a mode with .dlls dynamic linking instead of what they release which is all static linked exactly to speed up incremental development. The "fast" case is C not C++.


> I believe Chromium development often uses a mode with .dlls dynamic linking instead of what they release which is all static linked exactly to speed up incremental development. The "fast" case is C not C++.

Bevy, a Rust ECS framework for building games (among other things), has a similar solution by offering a build/rust "feature" that enables dynamic linking (called "dynamic_linking"). https://bevy.org/learn/quick-start/getting-started/setup/#dy...


There's no Rust codebase that takes hours to compile cold unless 1) you're compiling a massive codebase in release mode with LTO enabled, in which case, you've asked for it, 2) you've ported Doom to the type system, or 3) you're compiling on a netbook.

I'm curious if this is tracked or observed somewhere; crater runs are a huge source of information, metrics about the compilation time of crates would be quite interesting.

I know some large orgs have this data for internal projects.

This page gives a very loose idea of how we're doing over time: https://perf.rust-lang.org/dashboard.html


Down and to the right is good, but the claim here is the average full release build is only 2 seconds?

Those are graphs of averages from across the benchmarking suite, which you can read much more information about here: https://kobzol.github.io/rust/rustc/2023/08/18/rustc-benchma...

First of all if you have the money get an official diagnosis. While self diagnosis is often right, ADHD symptoms can have overlap with many other things so it is better to be sure.

Now want a quick fix? If you can, get medication. It doesn't work for all people with ADHD but for those that it does it will give you the most bang for the buck.

Now there is coping strategies. Therapists can help a lot. There is also people offering ADHD coaching. This is great because the coaches tend to have ADHD themselves and understand you. It helped me personally a lot but be warned that everyone can offer coaching so quality may wary.

Last part is lifestyle. Sport. It is not optional. Running is amazing and will help you a lot but if you are not fit enough yet, walk. Walk every day for at least 30min. You need to. Also personally for me reading a physical book for at least 30min a day makes a huge, huge difference. Diet is important but what works varies from ADHD person to person. For me cutting out processed sugar was a good step.

Also no caffeine. This may also vary but completely cutting it helped me personally a lot. Yes, it helps somewhat with executive function but only in the short term and does more harm than good in the long term. Generally any form form of self medication be it alcohol, weed and so on, cut it out. Again get proper medication if you can.

Honestly accepting that you have ADHD or well at least some form of neurodivergency is already the biggest step. It gets so much easier once you learn how to properly manage it.


https://borretti.me/article/notes-on-managing-adhd

Came across this a few months ago on HN here and there’s a fair bit of exposition on things you’ve mentioned. My personal takeaway from it was to try Todoist, which has been a complete game changer in my life. I’ve used other systems before but something about Todoist worked better for my brain (plus the mobile integration is awesome… my second best over the years was org-mode but the mobile story is way too clunky)


+1, Todoist has changed things for me drastically.

I was diagnosed with ADHD a year and a half ago in my ~mid 30s. The meds (Vyvanse) help somewhat, but the real key to improvement for me has been using Todoist.

IME the real trick is using it consistently, and for everything. My routines (e.g. morning routine: meds, eat, coffee, brush teeth, brush the dog's teeth, etc etc) are all in Todoist, not because I struggle to focus on getting that stuff done in the morning (well, sometimes, perhaps) but because starting the day with do-easy-thing, mark-it-done, repeat, sets up the rest of the day to be run by Todoist instead of the bit of my brain that goes "I know we should be getting ready to leave but WHAT IF YOU WROTE AN APP TO DO THIS COOL THING, JUST QUICKLY TRY THAT NOW, YOU CAN LEAVE AFTER".

I had a similar experience with org-mode too. It was great at work where I'm at my desk all day, and made a huge difference, but not having a good mobile experience makes it impractical for day-to-day home use.


That was 100% the key for me too: put absolutely everything into it that I can’t address immediately, both work and life.

I did use org-mode like that too (all of life into it, not just work) when I was working from home but both capture and viewing when away from the laptop just had too much friction.


They are free to use AI and they are free to post their music on other sides that allow AI.

I think you need hard rules to make it not completely subjective.


From the original post:

    We reserve the right to remove any music on suspicion of being AI generated.
Sounds completely subjective if you ask me.

"Your band was formed after 2023, we will ignore you even if you aren't AI"

By the end of 2026 the AI/no-AI thing is debate is going to be dead because there will be no way to know the difference. This is almost true right now, it just is going to take the general public a while to catch up.

One distinction which could be made: I would like to see bands that are humans because I want to physically attend and enjoy concerts. If the "artist" has never played a concert I don't want to listen to them. Which expands a whole new grey area..


There is no shared appreciation for vibe coding.

If it solves a problem, good for you but I don't think people should put their vibe coded projects online. They don't have any value.

There are delusional people who create vibe coded pull requests to open source projects and they believe they are actually contributing value. No they only create work for the maintainers that have to review the subpar code.

As for your use case, are there really no royalty free drum beats that you could use? Not to mention you could probably learn to create your own beats in Ableton in one weekend. You are cheating yourself.


QBE might be more to your liking: https://c9x.me/compile/

It is used in the Hare language


Especially as there is a decent working BasiliskII port for the PlayStation Portable with its 333MHz single-core MIPS CPU.

So this should be much easier.


Red Hat pushing for the disaster that is Wayland has set the Linux Desktop back decades.

It is the Microsoft of the Linux world.


Why is Wayland a disaster? Most of the Linux community is strongly in favor of it.

I'm sorry but this is just completely disconnected from reality. Wayland is being successfully used every single day. Just because you don't like something doesn't mean it's inherently bad.

[dead]


And that's fine! No one cares! Keep using it!

Or like 10 senior engineers in mid sized companies in Europe.

I wish every engineer were paid FAANG money.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: