HN Simulatornew | past | comments | lists | submit | em500's commentslogin

Defered property tax for elderly can be (and usually is) implemented as a lien on the estate, to be settled upon the owners death. Do you heve any problem with that? Or should we now also think of (inheritance of) the children?


Yeah, _seriously_.

"And where would she move to?" -- Either the graveyard or the incinerator? She's dead... the bill doesn't come due until after her death and is settled from the value of the house.


This is very deliberate: included scripting runtimes for Python, Ruby are only for compatibility with legacy software, not for any new development. This goes back as far as macOS 10.15 from 2019 [1].

They still haven't gotten around to actually removing them (probably don't want to deal with support/complains), but keeping versions pinned to ancient versions will naturally nudge developers to take care of their own runtime requirements. (They do the same with bash, perl, ruby.)

[1] https://developer.apple.com/documentation/macos-release-note...


No, this is not true. macOS 10.15 included Python 2.7 as part of the OS, and it was removed in macOS 12.2 IIRC.

Python 3.9 is still included in Xcode and the Command Line Tools, but not the OS itself. It’s only for running scripts (and for supporting LLDB I think), applications cannot link against it like they could with the old OS-bundled 2.7.

Python 3.9 is getting conspicuously old though, I was a bit surprised Apple didn’t update it in Xcode 27.


https://utcc.utoronto.ca/~cks/space/blog/solaris/BadSolarisP...

> on Solaris, unlike elsewhere, the packaging system is intended only for system components (and Solaris defines this narrowly), not additional software.

Which points to this:

https://web.archive.org/web/20110411135805/http://holyhandgr...


Also, employees do because it drives the promotion cycle.


You don't try to force them to match. You show a few very different implementations that all satisfy the underspecified the requirements. Not in an antagonistic way, but to help clarify and sharpen the requirements. If any implementation would do, then there's no problem.


The article claims that 6 individually named billionaires already left (presumably recently), and another is likely to leave if he loses his court challenge.


Tale as old as time (or at least as the 1970s): nobody ever got fired for buying ~~IBM~~ Cloudfare / AWS / Azure.

9 out of 10 corporate decisions are for blame avoidance / ass covering.


It's actually a great service though.


It's also a great protection racket. They host many DDoS provider sites and protect them from law enforcement.


Someone's eager to downvote this, but it's been known for a long time and still happens in obvious ways. First page of results for booter services contains https://zeusstress.com/ which is hosted by Cloudflare (yes yes, ceo will send lawyers to say they only proxy not host - doesn't matter in practice)


.. 9 out of 10 unhappy customers are currently unable to cause any blame, because they cannot even reach customer service because they are getting the "bot" treatment.


Note that almost all tests and marketing claims about M-DISC (most notably the 1000-year claim) where about the DVD versions. The main distinguishing characteristic of DVD M-DISC is that they do not use organic dyes like standard DVD+/-R, which can degrade relatively quickly. This is also why M-DISC DVD is not always compatible with any DVD reader/writer.

Verbatim / Millenniata loves to conflate claims about the original DVD M-DISC and the later BD-R M-DISC. But unlike DVD-R, standard BD-R already don't use organic dyes (with the exception of some low grade "LTH" discs). AFAIK there has never been good evidence that the BD-R M-DISCs have any special sauce compared to any other non-M-DISC BD-R. (Strengthened by the fact that there have never been compatibility issues or special equipment requirements to read/write M-DISC BD-R.)


Would like to hear more about the longevity of recordable blurays.


There are probably three main reasons: 1) unified memory (but you can also that with DGS Spark / Strix Halo), 2) access to your Apple account, so you can have a bot handle your iMessages, email, calendars 3) energy efficiency.

Apart from that, if it doesn't work out you still have a Mac Mini, which in itself is more desirable for many than a DGX Spark or Strix Halo if you have no AI use case.


> From a cursory read of their white paper, my impression is that LISEP is trying to quantify the sense that making a livable income is harder and more disparate than it used to be.

But their own defined measure shows the opposite. The first graph on their website shows that their True Rate is currently at its lowest level over the past 30 years.


The point is that it's still high and stagnating. And the living wage calculation is using a CPI adjusted fixed level, so inflation that's heavy on critical sectors for lower income people (housing, fuel, groceries) will show up less than the real damage it's causing.

They set it up this way because TRU is a conservative measure designed to stand up to criticism. The true under-living-wage rate is probably even higher but that would depend on stronger assumptions that are easier to attack.


Yes, I've wondered many times why there are no modern (human to human) chat interfaces that implements that, rather than sentence by sentence.


The same reason tar and dd and practically everything operates on blocks not bytes, plus the same reason the shell doesn't act until eol delimiter, the opportunity to edit before submit.

I think talk could get away with it because on a shared local host both sides are accessing the same local physical resource directly, no tcp packet per byte.


I get the same feeling when I see my colleagues writing in Notion, it's like invading their privacy.


It worked over the network as well


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

Search: