Looks like a very tiny LUT, perhaps it's all in SIMD registers.
In any case, for anything to go at 12 GB/s, the LUT needs to be tiny and pretty much in SIMD register(s).
Any indirect memory accesses would drastically slow things down, even if it's in L1 cache [0]. At least by an order of magnitude.
Even when using something like x86 V[P]GATHER [0] (element-wise vector random access load). X86 gather is currently only slightly better than scalar code, even if all the data is on same cache line present in L1D!
At least in the case of the Digital Euro, one of the explicitly documented goals for the scheme is to alleviate dependence on US payment processors within Europe
> The experience with pandemic emergency payments has brought forward an idea that was already gaining increased attention at central banks around the world, that is, central bank digital currency (CBDC). Legislation has proposed that each American have an account at the Fed in which digital dollars could be deposited, as liabilities of the Federal Reserve Banks, which could be used for emergency payments
I'm fairly noobish at understanding all this stuff, but as I understand it there are severe structural issues with the existing banking system that make a completely new mechanism desirable. For example by depositing cash into traditional accounts, it is also equivalent to providing capital to traditional banks to loan from. It would therefore be difficult to supply cash to end users without also increasing the availability of credit, which may be undesirable for any number of policy reasons.
the most obvious case is that people don't have a bank account or are 'underbanked' in the US that amounts to about a quarter of the population[1]. I think covid has shown what a mess it is to get everyone their relief money. If everyone had a digital account with the FED it'd literally be a few clicks of a button.
I moved to XPS 15 as my first non-Mac machine in over 10 years, and I must say I'm far from impressed by the build quality.
These laptops are gorgeous new, but they are SO fragile. One of the screen hinges is broken, I've replaced numerous keys, the keyboard is now developing some debounce/key registration issue all over the right-hand side, the speakers are both blown (left first then the right), the trackpad sits 0.5cm above the case (needs replaced), the glue holding the rubber to the bottom of the case expanded with heat and leaked out everywhere. Probably more I've forgotten
I'd still consider buying another, but I'd also strongly consider changing vendors once this machine finally dies
The fragility of Dell's consumer laptops is why I continue to buy Lenovo's which are less sleek but have better durability and run Linux just fine. In recent memory I've had an X1 Carbon and X1 Carbon Extreme Gen 1 and been very satisfied.
Lenovo are also way better at warranty. In my experience they just asked for the serial number of the ThinkPad, it was still covered and they accepted it (and fixed it). It was an used laptop.
Dell OTOH asked for the original receipt of purchase, that of course I didn't have because that also was an used laptop.
Also, the latitude series is way better than the xps line. I've got the latitude 7390 from dell and it's just marvelous.
So yeah, if you're buying new, dell or Lenovo ThinkPad (I'd recommend a ThinkPad though).
If you're buying second hand, ThinkPad is the way.
Exactly my thoughts too. I love the look and build of the Dell's but the Lenovos, while ugly, are so tough and so easy and cheap to repair. I buy all ThinkPads these days (most recently the T580 and T490, both of which are amazing and run Fedora like a dream, out of the box).
I have an XPS 13. I paid for the default "basic warranty." This week my fans started wobbling, causing lots of noise. I called Dell, told them I was using Linux, then they immediately offered to send someone in-person (with pandemic safety precautions) to fix it. And they did. It took 15 minutes for my fan to be replaced once they arrived. The person was very helpful, and they improved my boot time, too, by setting the clock in my BIOS.
My experience is total opposite. I had horrible hardware experience with MacBook Pro. Battery being blown up, broken hinges, keyboard skipping... My XPS has been working amazingly fine. ¯\_(ツ)_/¯
Same, XPS 15 9570 (2 years old I believe). It's almost as good as new. A little electrical whining when charging and putting the ear against it, but that's since day one. I've kept a cloth in between the screen and keyboard, kept everything clean just by rubbing a cloth a few times.
FWIW my late 2013, 15" MacBook Pro seems to me just as good as new. Never had to replace the battery or have any kind of service done on it at all.
I kind of want to buy a new model but this thing just keeps going so I have no legitimate reason to do so. Honestly, I really love the machine. The fact that I'll get at least eight years out of it, as I did from my last MBP, means I'll definitely buy another MacBook Pro.
You don't buy a dell without the four year "come to my house and fix it" service contract. Basically you can get a dell for $1000 and it will fall apart or you can buy the same machine for $1400 and it wont, and if it does, they show up the next day and fix it or replace it. I sometimes wonder if they actually do quality binning or have a different production line. But basically a Dell costs $400 more than you think. And they are fantastic, in my experience.
I was in the UK on business when my keyboard broke, and the next day a chap showed up with a UK keyboard. When I pointed out it was a US keyboard. Didn't bat an eye, just walked back out to his van and came back with a US one.
Buy a thinkpad. Dell’s build quality and support are atrocious compared to Lenovo.
Lenovo doesn’t hold a candle to Apple still but Dell is still bottom barrel. Have you ever tried calling Dell to get something fixed? Good luck!
Thinkpads are tanks and with Lenovo they either fix a hardware issue by having you send it to them or you can request a customer replaceable part and fix it yourself.
The problem is Lenovo machines look and feel like PCs, and that's not a complement. I got the XPS specifically for the trackpad, its the only one around that I know of that handles any way remotely like a MacBook's.
In fairness, most people just ignored the latitude line from dell and just focus on the xps line. I wouldn't trade my latitude 7390 for an xps 13, honestly.
I had similar issues and will say that quality varies wildly between models. I had a bunch of 9560s that all had awful problems (to the point of return) until I finally returned the last one and got a 9570 (I had done this enough times that the new model had come out.) It's had absolutely no issues.
XPS line is plagued by constant quality control issues that Dell doesn't fix year after year, generation after generation. With XPS 15 look up the expanding/exploding battery issue, thermal throttling etc. Mine (XPS 15 9550) also had issues with the hinge, the power cable, having to fight dell to get an adapter to fit the second drive which they stated stated it supports, and intense fan noise then especially after the Meltdown mitigations were applied I gave up on it completely.
Their strength is in quality peripherals, ie screen etc, but their weakness is garbage quality control and it's so overpriced for that.
If you can, avoid XPS! If you can't well .. purchase extended warranty with the on-site option, you're gonna need it ..
Noticed this a few times, where race is associated with some bad behaviour as if it made matters any worse. What does it matter if the developers were Turkish?
edit: are the downvotes because you believe race matters in this case, or some other problem with the comment?
I didn’t downvote you, but “Team of Turkish developers” is just how original author of the extension refers to the new owner in his original announcement.
...and I'm relatively certain they wanted to communicate that the new owners are based in Turkey, not that their developer team is strictly of Turkish ethnicity. They probably didn't check whether there might be Kurds or Circassians on the team.
My impression was that Turkish referred to nationality, not race in this case. The impression is that electronic law and order in Turkey are different than in California.
I just read it as Turkish= out of the country + basically unreachable. Based on the due diligence (or lack thereof) they could actually be from anywhere. He has no idea.
For single node sure, but the moment you have some set of jobs requiring a multi node setup, the chance of wanting to find yourself in a situation where the cluster has essentially bricked itself due to a momentary power outage reduces to zero really quickly.
The only place etcd might not pay off is in disposable dev environments or something, but do you really want your prod setup to page only to discover a complete cluster rebuild is necessary to resolve the problem?
There are various levels of outages you may encounter with an etcd outage, but it shouldn't take your workloads completely offline. The cluster API will be offline, but the workloads will keep on chugging. I think with the decoupling of etcd and the expectation that this might happen, we'd see more improvements on how to (gracefully) handle these situations.
Also, there was a bug with kube api where it wouldn't failover to other etcd members during an outage. So I would say most customers have ran kubernetes with a "single backend" at some point.
Classic bait-and-switch. This essentially happens with every review site after they build up enough brand awareness to pull it off. I guess it happens because from the perspective of the company it makes total sense to try. Why earn pennies on the dollar from e.g. ad clicks when you can get huge lumpy (and possibly regular) payouts for much less work in much less time
> Why earn pennies on the dollar from e.g. ad clicks when you can get huge lumpy (and possibly regular) payouts for much less work in much less time
When things are working well, the answer is because honesty is a better policy in the long run. Impartiality, and a reputation for impartiality, is why Which? still exists, at the age of 63. [0][1]
Yes, every tech nerd is mocking their PC tests, because they are just like a vaccuum cleaner test: unbox, set-up, do mainstream stuff, like writing mails and Word documents. No discussion of GDDR5 vs. GDDR4 or such nonsense.
It's a fantastic resource when you don't know what to look for (until today you never had any use for the tool you now consider buying) and it's not tech (then I tend to look to Wirecutter, for all its faults and controversies).
> every tech nerd is mocking their PC tests, because they are just like a vaccuum cleaner test: unbox, set-up, do mainstream stuff, like writing mails and Word documents
That still sounds like a useful test, if only to punish bundling of useless bloatware.
because honesty is a better policy in the long run
SV doesn't optimize for the long run. It only cares about the next quarter, or until the buyout comes. Everyone knows the phrase "exit strategy," but nobody knows the phrase "quality and service."
In my experience, 1%† of the people in the SV bubble are doing it to make a quality product. They're just there to make a quick buck.
AWS in particular seem to have a carefully refined technical sales/certification/advocacy channel whose main product is those fucking stupid architecture diagrams. Hello world service with $4000/mo. worth of geo-replicated backing databases, CloudWatch alarms, API Gateway instances, WAF etc.
But don't let it encourage you to think serverless has no value, or it can't be done portably or cheaply. It has its sweet spots just like everything else.
Reminds of something that was on the HN frontpage some month ago, where readers are not sure if it's a parody or not, because of the architecture you're required to deploy yourself to use this new "Perspective" product. Direct link to the architecture, that in the end serves the use case of generating a diagram of your AWS resources: https://d1.awsstatic.com/Solutions/Solutions%20Category%20Te...
Reading this made me remember that back in the day the AWS selling point was "here you can create virtual machines with few clicks and have it instantly instead of waiting 30 min for you colocated server to be ready" but now it seems to be "here is a bunch of random expensive tools, please, produce as much stuff as possible and share the word that having servers is bad™".
This field used to be inspiring, but now I see the ideia of having a server being sold as the plague and lots of negativity towards people who are good at servers. They are not seen as another human being but the "other".
Also I can't understand why one would prefer to pay that much for such complexity.
It seems unsustainable for me, not to mention the new generation being spoon fed that that is way to go makes me concerned about the future of open computing.
"Also I can't understand why one would prefer to pay that much for such complexity."
If there is one thing that dealing with AWS reps has taught me, it's that this was 100% by customers. I swear to god, AWS doesn't do anything without customers asking for it.
If you are wondering why products are build in AWS, it's because people wanted to give them money for this. Say what you want, but this isn't something are pushing on us. This is something "we" push on them to provide.
Your response made me smile. Glad to see there are still reasonable folks out there.
Working for a startup without a "resume-driven-development" CTO gave me the freedom to go "servermore" architecture with max flexibility.
For all the talk about resume driven development, I am hiring now, and will say that people who have solved their problems by learning more about Linux and such sound way more impressive than those who list out passing familiarity with a bunch of high level services. The first style of resume really stands out. The second is a dime a dozen.
To make an analogy, it's like hiring a carpenter based on the number of tools they have. NO. Show me your skill with a hammer and chisel, and I'll assume you can figure out the rest.
> not to mention the new generation being spoon fed that that is way to go
The new generation is always joining one cargo cult or another, that's why competent technical leadership is important. Remember when noSQL was the best thing since sliced bread?
Serverless can be a good option if you have large and unpredictable transient loads.
Like any architectural choice, you need to consider the tradeoffs and suitability for your use case. A TODO app probably doesn't need to be built with a serverless SOA.
