If we keep current spending the same. We could reduce the % the top 1% bare by reducing inequality and by having the 99% earning and paying more tax.
Or we could reduce taxes for the 1% and reduce spending which would likely increase inequality.
767 karma · joined August 22, 2017
If we keep current spending the same. We could reduce the % the top 1% bare by reducing inequality and by having the 99% earning and paying more tax.
Or we could reduce taxes for the 1% and reduce spending which would likely increase inequality.
Its a shame those links can't have an alttext to show the real link.
I don't want to go back to OS X, but its hard to find good build quality and a high res screen.
Also, my battery was terrible after a couple of years. I had it plugged in as well. I bought a replacement this year and it was easy enough to switch out. Hopefully I can just keep this going and use it as an RDP machine.
[1] https://www.reddit.com/r/Dell/comments/onvh42/xps_9560_tpm_d...
[1] https://confluence.jetbrains.com/display/JBR/JetBrains+Runti...
Horses for courses though. If I didn't have space for a desktop I'd be happy to have the XPS 15.
Multi-monitor is my big requirement when it comes to development. The 15" screen is good, but it doesn't beat a proper side by side setup.
New laws can be iteratively created rather than relying on extremely old documents and lawyers/historians who attempt to decipher what was intended and how that relates to modern times.
If the US constitution was converted into a set of laws and then deleted, what do you think would happen? Attempts to be made to change the laws, some would pass, some would fail, but the passing of those laws would still be democratic if those making them were democratically elected.
- NHS takes care of emergencies. There is no stress of payment in these situations.
- I have private medical insurance through work. Its done by salary sacrifice so I can choose to take the money instead.
- I can buy private medical insurance separately. Providers like Vitality[1] offer things like Apple Watches and discount gym membership. Private medical insurance is generally quite cheap (Vitality just quoted me £40/month) as emergency care is done by the NHS.
- You can use private healthcare to speed up things that might take a while or you might not get an NHS referral for.
Of course there's some problems with the NHS in terms of wait times, but I believe that's more of an issue of funding. In the UK I feel like I have choice that won't break the bank and I'm also not going to die because I can't pay.
[1] https://www.vitality.co.uk/rewards/partners/active-rewards/a...
All to push a story which started with an off screen killing of Nomad.
The trading platforms I've worked on tend to order things into a single stream that you can act upon. This helps with testing, race conditions, auditability. You will want to be able to replay an exact series of events to recreate conditions.
LMAX Disruptor[1] and Aeron[2] are two open source examples of something widely used, either using the libraries themselves or as concepts.
Some things that trading systems (generally?) need which you may not, which might simplify your architecture:
- Every message must be delivered and in order. UDP is usually used over TCP, as the platform will likely want more control over handling missed messages. - It will be common to have read/write applications that need to add a message as a response. Writing is difficult as you need to be quick, otherwise a subsequent message from another application might invalidate your message.
Do subscribers need older data? How do dropped packets impact the system? Can they just be forgotten? What latency requirements do you have? Do subscribers also write to the same stream?
- [1] https://lmax-exchange.github.io/disruptor/ - [2] https://github.com/real-logic/aeron
With trading platforms, they last for years, decades maybe. They're created with some ideas around how to manage performance and to support evolving requirements. Developers know this thing is going to be around for a long time, so its treated as such. Years down the line, you start creating a new platform and look to do a long migration to keep clients happy because you can't just turn off their favourite functionality.
Modern AAA FPS games seem to be the complete opposite. Reinvent significant amounts every release. Dump the old game as the new one is released. Much seems to be from scratch. The BF2042 scoreboard issue seems like it should be almost off the shelf. There also seems to be this big shift towards short release cycles which pushes even more churn and reinventing the wheel. Look and feel must be updated to keep things "fresh". Although most of the popular games on Steam[1] are older games that have been around for years.
So many places to shave a yak, I'm surprised games get shipped at all.
Of course take all of this comment as an outsider who just yearns for the old days of cool mods and custom servers.
> The Valve Archive is a fan-run repository...
https://valvearchive.com/about/
Hopefully, it stays, but I wouldn't want to bet on it.
We’re now heavily moving towards containers and the primary motivator is choice of languages and standardisation. Being bare metal is fine when you use a single language, but you’ll find you shoehorn other languages with the same process. Interpreted languages (Node/Python) are a nightmare and you’ll have to find a pattern for running multiple versions on the same host.
Containers is just a real nice deployment unit and is well supported by other tools.
If you are really keen on this path, do consider up front how you will handle version upgrades of the runtime or dependencies.
Everything is so slow. Back when Freeview started being a thing in the UK, TVs then had a rapid TV Guide built in and everything felt instant. Now every screen change is a pause. I've got a PS5 so I'm much happier using that for apps.
It feels like feature phones were slow and laggy, we then got responsive smartphones. TVs were responsive, now they're slow and laggy.
That way if a dependency does a minor upgrade that breaks your code but you also need some new functionality, you could depend on the old code in a particular package and new code in another.
Cool if you work in the City. My boss and I did it on our lunch break.
Applications are more like buildings which need to be maintained. Perhaps you could consider it a multi-use building with many tenants and sometimes under attack.
> inout(reg) a,
inout looks like a function but I don't see how that works with the `a` variable. Is this some magic specifically for asm!?
If I need to bump a version with Semver, I can estimate how long it will take. Going from log4j 1.2.17 to 2.17.1 will be bigger than going from 2.16.0 to 2.17.0. And 2.17.0 to 2.17.1 should be easy.
I completely agree with your last paragraph, though. I'll take a collection of utilities from a well known organisation over many tiny dependencies any day.
Go to Preferences -> Local Storage -> Store a copy of all originals at the specified location.[1]
I then sync the folder to S3.
[1] https://helpx.adobe.com/lightroom-cc/using/preferences.html
There should be a non-criminal route for helping drug addicts that doesn't result in prison.
We're already seeing similar parallel in Finance with End User Computing[0] where non-developers (traders, etc) are using tools like Python, Jupyter, etc as part of their jobs.
I don't ever see it replacing developers though. Maybe if your entire job is workflow automation, sure, but developers will focus on solutions that are difficult to do with Low/No Code tools.