Preferences

maxnoe
Joined 1,179 karma

  1. But on any modern CPU, clock speed won't be constant. It's not compile time constant, nor a runtime constant. Its variable over time. You'd have to record the clock speed over time and the ticks, so why not just record actual time?
  2. Would this argument still apply if I need to store a uuidv4 anyway in the table?

    And I'd likely want a unique constraint on that?

  3. Fraktur is often associated with the German far right, because it's a mostly German thing that nationalists can hang on to.

    Funnily enough, it was Goebbels who banned it and required everyone to change to Latin scripts.

  4. The book is quite old actually, not sure if "this day and age" still applies to it
  5. Completely new tunnel, but it will be connected to LHC, as they will use LHC to pre accelerate the particles.

    Almost all accelerators built at CERN are still active and are a chain of pre-accelerator for LHC now:

    https://en.wikipedia.org/wiki/Large_Hadron_Collider#/media/F...

  6. They integrate with radicale since May this year for card- and caldav

    https://opencloud.eu/en/news/opencloud-calendar-and-contact-...

  7. I cannot... Geoblockig European IPs?
  8. > That being said, I probably have 300 knifes in my home

    Don't forget the follow up

  9. > WGS84 sucks for mapping a sphere.

    WGS84 is not a map projection, it's a geodetic reference frame prescribing a reference ellipsoid and reference positions of ground stations.

    https://en.m.wikipedia.org/wiki/World_Geodetic_System#WGS84

  10. The idea here is to have a clock that actually ticks faster and to redefine the second in terms of that new, faster ticking speed.
  11. Since my DNS provider(IONOS) has an API and there is a plugin for my Webserver (caddy), DNS certificates were completely painless, even for *.<my domain>.

    The solutions exist, depensa on the providers and your client.

  12. This project is way older than (rootless) podman.
  13. Author drops that he owns a Leica M11 in a half sentence.

    Most people who consider prices don't.

  14. The anti proton was very fast, but it needs to capture a positron to become an antimatter hydrogen atom. This happens after the anti proton was slowed down.
  15. Organizations cannot yet create tokens, only the setting up trusted publishing is supported, but that only works on four providers and e.g. not in self hosted gitlabs.
  16. HTML + CSS is only half of the equation. The renderer is also important. So you need a layout engine that turns the HTML+CSS into something you can view.

    Most of the time, this is one of the browser engines, but there are many more things.

    There is e.g. weasyprint to produce PDFs from HTML and CSS, which would be the closest alternative to LaTeX taking HTML+CSS as input.

    For simple documents, it's a much cleaner alternative, I used it to autogenerate documents in a python backend.

  17. I've been using microtype with lualatex, fontspec and Opentype fonts for years.

    What doesn't work?

  18. The current goal is to redefine the second in terms of an optical frequency once clocks are available that offer a higher precision than 1 second over the lifetime of the universe.

    https://www.nist.gov/si-redefinition/second-future

  19. Not for gaming, but this was developed for checking plots: https://github.com/hdembinski/monolens

    And works cross platform.

  20. You can express rest energy in electron volt, a unit of energy. The energy an electron gains by being accelerated in an electric field of 1 Volt.

    But since E=mc², you can say the mass is X eV/c² and then people become lazy and forget the c² or even define a new system of units in which c=1.

  21. Both. You get untreated, just with iodine and iodine + fluoride.

    https://www.bad-reichenhaller.de/de/produkte/alpensalze/alpe...

  22. All checkers games I ever played started with a long negotiation about the rules...
  23. I understood the comment as "Google <the long version I provided> to get more info"
  24. Please read Articles 1 to 19 of the German Constitution.

    It's a worthwhile read for anyone.

  25. Sorry, there is a "not" missing there.

    A remaining issue is that it is not easy to get proper TAI on most systems.

  26. The first clock precise enough to even measure the irregularity of Earth rotation was only build in 1934.

    Before, it was simply the best clock available.

  27. TAI is not a time zone. Timezones are a concept of civil time keeping, that is tied to the UTC time scale.

    TAI is a separate time scale and it is used to define UTC.

    There is now CLOCK_TAI in Linux [1], tai_clock [2] in c++ and of course several high level libraries in many languages (e.g. astropy.time in Python [3])

    There are three things you want in a time scale: * Monotonically Increasing * Ticking with a fixed frequency, i.e. an integer multiple of the SI second * Aligned with the solar day

    Unfortunately, as always, you can only chose 2 out of the 3.

    TAI is 1 + 2, atomic clocks using the caesiun standard ticking at the frequency that is the definition of the SI second forever Increasing.

    Then there is UT1, which is 1 + 3 (at least as long as no major disaster happens...). It is purely the orientation of the Earth, measured with radio telescopes.

    UTC is 2 + 3, defined with the help of both. It ticks the SI seconds of TAI, but leap seconds are inserted at two possible time slots per year to keep it within 1 second of UT1. The last part is under discussion to be changed to a much longer time, practically eliminating future leap seconds.

    The issue then is that POSIX chose the wrong standard for numerical system clocks. And now it is pretty hard to change and it can also be argued that for performance reasons, it shouldn't be changed, as you more often need the civil time than the monotonic time.

    The remaining issues are:

    * On many systems, it's simple to get TAI * Many software systems do not accept the complexity of this topic and instead just return the wrong answer using simplified assumptions, e.g. of no leap seconds in UTC * There is no standardized way to handle the leap seconds in the Unix time stamp, so on days around the introduction of leap second, the relationship between the Unix timestamp and the actual UTC or TAI time is not clear, several versions exist and that results in uncertainty up to two seconds. * There might be a negative leap second one day, and nothing is ready for it

    [1] https://www.man7.org/linux/man-pages/man7/vdso.7.html [2] https://en.cppreference.com/w/cpp/chrono/tai_clock [3] https://docs.astropy.org/en/stable/time/index.html

  28. The headline is BS. At least completely misleading.

    They only compare to some strange, Russian direct train.

    The reference should be the current best connection, which would have one train switch.

    The difference between this new connection and the fastest connection with one switch is ~15 minutes.

This user hasn’t submitted anything.

Keyboard Shortcuts

Story Lists

j
Next story
k
Previous story
Shift+j
Last story
Shift+k
First story
o Enter
Go to story URL
c
Go to comments
u
Go to author

Navigation

Shift+t
Go to top stories
Shift+n
Go to new stories
Shift+b
Go to best stories
Shift+a
Go to Ask HN
Shift+s
Go to Show HN

Miscellaneous

?
Show this modal