Hacker News new | past | comments | ask | show | jobs | submit
  1. How do you remove all company monitoring from the device? Does IT relinquish root access?
  2. I think it will be the software developers that lean more into the kind of skills you see in technical product managers, or maybe vice-versa.
  3. "I'll break my staff, bury it certain fathoms in the earth, and deeper than did ever plummet sound, I'll drown my book" -- The Tempest (1611)
  4. If you don't want people to find it for such an extended time, it needs to be not just buried, but buried buried ;)
  5. This is worth considering in the context of driving at night.

    I used to get terrible eye strain, causing fatigue and sleepiness. Obviously not good.

    Then I bought a Saab 900. It had a 'night mode' that disabled all dials except the speedo. The lights went off and the dial went down. (It came back on if it needed to alert you of something, say low fuel.) [0]

    This made a radical difference, and led me to the dash-brightness dial that nobody ever touches. Turns out if you turn that way down, reducing the contrast between you and the road, it's actually enough to get you 90% there. Because you probably don't drive a 1992 Saab (more's the pity).

    [0]: https://www.youtube.com/watch?v=KIfzUqYEkiw

  6. Right but it's not magic as you cannot predict networking delays.

    The max clock skew also has to pick between A and C, in underestimates you lose serializability, in overestimates you pay in write latency.

  7. Yoon is arguing some ridiculous excuses which would have been funny if this was not serious.

    Sounds like a standard "democratic leader" these days.

  8. Slight disagreement here.

    Allocation is perceived as slow because it is. Getting memory from the OS is somewhat expensive because a page of memory needs to be allocated and stored off. Getting memory from traditional allocators is expensive because freespace needs to be tracked. When you say "I need 5 bytes" the allocator needs to find 5 free bytes to give back to you.

    Bump allocators are fast because the operation of "I need 5 bytes" is incrementing the allocation pointer forward by 5 bytes and maybe doing a new page allocation if that's exhausted.

    GC allocators are fast because they are generally bump allocators! The only difference is that when exhaustion happens the GC says "I need to run a GC".

    Traditional allocators are a bit slower because they are typically something like an arena with skiplists used to find free space. When you free up memory, that skiplist needs to be updated.

    But further, unlike bump and GC allocators another fault of traditional allocators is they have a tendency to scatter memory which has a negative impact on CPU cache performance. With the assumption that related memory tends to be allocated at the same time, GCs and bump allocators will colocate memory. But, because of the skiplist, traditional allocators will scattershot allocations to avoid free memory fragmentation.

    All this said, for most apps this doesn't matter a whole lot. However, if you are doing a CPU/memory intense operation then this is stuff to know.

  9. > Traditional allocators are fast

    Really it's allocators in general. Allocations are perceived as expensive only because they are mostly dependent on the amortized cost of prior deallocations. As an extreme example, even GCs can be fast if you avoid deallocation because most typically have a long-lived object heap that rarely gets collected - so if you keep things around that can be long-lived (pooling) their cost mostly goes away.

  10. Employers, government or not, still wield far too much power over the personal lives of employees. I think it is rather meaningless to try and understand why RTO is en vogue now.

    Why is the discussion so rarely focused on the fact that your boss can demand that you uplift your life or else you're fired, immediately and with impunity, and what you have to say about it means absolutely nothing?

    Maybe I am baffled by this because I live and work in Europe where the relationship is a bit better (though I am not sure for how much longer it will remain as such). Americans seem very content to allow this behavior as normal because, obviously, other employees (but not me, I am a great employee!) must serve their stakeholders better so we can gain every bit of efficiency and increase precious income in the economy.

  11. Why would you assume iOS, not being the cheap option for a smartphone, would choose to emulate a cheap calculator?

    There were non-cheap calculators in the 1980s, too, that did proper evaluation. The ones I remember had keys for parentheses, though, allowing you to enter, for example

      (3 + 4) * 7 =
    
    to get 49.

    For an example see the TI-25 at http://www.datamath.org/Sci/Slimline/TI-25.htm

  12. When I used to teach math, the difference in how calculators handled precedence was always a problem. I would tell students to enter 1+2×3 into their calculators and if they got 9,¹ they should throw away the calculator and buy one that worked properly. Not respecting the precedence rules is bad design.

    The calculator built into Windows (at least back then, maybe they’ve changed it), gave 9 to my test instead of 7.

    1. If they got some number other than 9 or 7, I recommended dousing it in holy water, and then gasoline, burning it, encasing the ashes in concrete and dropping that concrete block into the deepest part of the ocean because that calculator is cursed.

  13. Just putting it out here - before the recentish redesign of ios's default calculator, it had a widely non-intuitive behavior. Due to how it looked I assumed it works as a standard four-function calculator, but it was actually storing the whole expression in memory and executing it as per the standard precedence rules.

    I do usually prefer the latter behavior, but without it being displayed as in more advanced calculators (it has been changed to show it) it's just not what I would expect at all, resulting in wrong calculations. But maybe it was just a "me-problem".

  14. Operator research preview

    https://openai.com/index/introducing-operator/
  15. Ask HN: Laid off employees, did the company ask you to return equipment?

  16. g.co, Google's official URL shortcut, is compromised

    https://gist.github.com/zachlatta/f86317493654b550c689dc6509973aa4
  17. Snowdrop OS – a homebrew operating system from scratch, in assembly language

    http://sebastianmihai.com/snowdrop/
  18. Show HN: Cs16.css – CSS library based on CS 1.6 UI

    https://cs16.samke.me
  19. A WebAssembly compiler that fits in a tweet

    https://wasmgroundup.com/blog/wasm-compiler-in-a-tweet/
  20. Opennote – Personalized Learning, Perfected

    https://opennote.me
  21. AI isn't going to kill the software industry

    https://dustinewers.com/ignore-the-grifters/
  22. 1,300 coins buried buried during Roman emperor Nero's reign found in England

    https://www.livescience.com/archaeology/romans/more-than-1-300-coins-buried-buried-during-roman-emperor-neros-reign-found-in-england
  23. How to improve your WFH lighting to reduce eye strain

    https://rustle.ca/posts/articles/work-from-home-lighting
  24. Every System is a Log: Avoiding coordination in distributed applications

    https://restate.dev/blog/every-system-is-a-log-avoiding-coordination-in-distributed-applications/
  25. Wild – A Fast Linker for Linux

    https://github.com/davidlattimore/wild
  26. Eki Bright – The Case for DIY Routing

    https://twocentstudios.com/2025/01/24/eki-bright-the-case-for-diy-routing/