Being 6'5" myself, I am worried I'd be blinded by the lamp when I stand up: to avoid adding a base under (an already bulky) base, is there a way to separate the lamp itself and have it wall/ceiling mounted (still pointing upwards)?
Thanks for confirmation, but anatomies of people, especially at the p5/p95 extremes, can be widely different: maybe I've got a very small head with a short forehead :)
So in a sense, I'd still like an option to mount it differently and more out of the way before splurging €1.2k + ~30% customs/VAT on something like this.
This even prompted me to check out comparable video fill lights on Aliexpress, and they also run around $1k (some at $500 with possibly a few gotchas about actual light output)
for comparable luminosity/wattage, so your price is actually not too shabby.
Hey Senko, did you consider using ZFS or BTRFS snapshotting feature to simplify some of the things you need?
For GH auth tokens, you could also pull that outside the sandbox, and have the agent push to a local clone exposed to the host, and local host with no agent automatically push on inotify inside the repo — eg. agent has access to your /agents/scratchpad/my-git-repo, and sync to actual git hosting service like GH (or Launchpad ;) happens with simple script outside it.
That's interesting, how does Chrome implement "sandboxing" in Windows and MacOS? For Linux, does it use the same underlying technology as Docker, Podman, LXD, LXC (cgroups, namespaces...)?
Or is a custom "sandboxing" implementation not relying on system level functions (eg. a VM with restricted functions)?
If the latter, I wonder if something like JRE or .NET CLR is still out there in larger numbers, but obviously, Chrome does have billions of users.
Yes, Chromium has "native" sandboxing on all those platforms, Windows [0] Linux [1] and MacOS [2].
Chromium uses both seccomp filtering as well as user namespaces (the technology that Docker/Podman use).
The Windows and MacOS sandboxing strategies are more "interesting" because I've seen very few (open source) programs that use those APIs as extensively as Chromium. On Windows, it makes use of AppContainer [3] (among other things), while on MacOS it uses the sparsely documented sandbox API [4], which I think was based on code from TrustedBSD?
this[0] page makes it seem 500~1000 cycles till 80% starting performance is common. So if you were charging it every other day from a 40~50 mile round trip commute, after 3~5 years you'd go to charging it every day.
As described there, this assumes slow overnight charging, and latest generation of batteries (not sure how viable that was the time of EV1).
Even LiOn batteries have charging patterns as the blocker to adoption, which means that practically, you'd get cars with less than 50% capacity by 2 years.
Also, not like it just keels over and dies, that's just the 80% performance criteria. Most people wouldn't need to replace the batteries at that point.
I am saying there is no evidence either way: they had contrasting experiences and one GP established this means that company has no standardized policies. Maybe they do, maybe they don't — I don't think we can definitively conclude anything.
I object to your conclusion that "they have no durable principles": not sure how do you get to that from two different experiences documented with a single paragraph.
This is becoming futile: this is not even about proof, but there not even being a full account of two cases you are basing your opinion on.
Obviously, you can derive any opinion you want out of that, but while I am used to terms like "probability" being misused like this, I've generally seen a higher standard at HN.
To each their own, though. Thank you for the discourse and have a good day.
I think Nintendo and Sony were almost the pioneers of "corporate shit": yes, Nintendo has a bit different style of gameplay they target, but their business practices have been corporate-protectionism for decades.
Even with sales tax being on consumption, rich people and their accountants always look how to reduce the burden: say, that trip to Hawaii was a business trip, and that expensive suit a business cost, and sometimes you can claim some of that is "wholesale" purchase to avoid it.
In jurisdictions using VAT (like most of Europe), there are whole schemes like that to effectively reduce your VAT burden through use of company purchasing.
In market dynamics, a worker becoming cheaper means that some employers will fight to hire/keep an employee on that surplus, thus driving the employment cost up for everybody else.
Yes, it probably would depend on positions and available talent, but overall and over a longer period, if applied universally to a market (say state like CA), it will be reasonable to expect salary increases (but not increase of how much is that worth because of increasing purchasing power, and increase in prices due to higher willingness to pay).
I believe it is a reasonable hypothesis that if payroll taxes were removed, 2nd order effect would be that employers have more money to offer for all positions, and in a market driven job market, prices would increase and thus salaries would converge to X+Y, yet they would be worth the same as X today.
Yes, likely not exactly the same (a bit more kept by employers in overcrowded job markets, a bit less in others), but it would essentially support the interpretation that most of that is really a tax that goes out of employee "budget", or their total comp.
Maybe the AI workloads running on it achieve escape velocity? ;)
reply