> Otherwise please use the original title, unless it is misleading or linkbait; don't editorialize.
There is already a presumption that "in early talks" means in discussion of possible acquisition/merger so I think this would be the time to deviate from the source's title.
Possibly like "Hyundai in discussion with Apple about electric car collaboration", or "Apple and Hyundai considering a joint venture for cars".
If you're in this thread "I built a PC, all my stuff has RGB, it's fine but I don't get it", try setting them all to the same color - you might be surprised how nice it looks. I set everything to white, but my roommate has a nice shade of purple he uses for everything. My real golden rule is absolutely no motion. Can't stand cycling rainbows or whatever.
It's a bit buried, but if you click through the link about how today is a big day for Observable, you'll notice it links to an article announcing that they raised their Series A today: $10.5M from Sequoia and Acrew.
This is really great, but RISC CPUs can have microcode too. Nothing stops them from doing that.
The big diff is load/store:
- Loads and stores are separate instructions in RISC and never implied by other ops. In CISC, you have orthogonality: most places that can take a register can also take a memory address.
- Because of load/store, you need fewer bits in the instruction encoding for encoding operands.
- Because you save bits in operands, you can have more bits to encode the register.
- Because you have more bits to encode the register, you can have more architectural registers, so compilers have an easier time doing register allocation and emit less spill code.
That might be an oversimplification since it totally skips the history lesson. But if we take RISC and CISC as trade offs you can make today, the trade off is as I say above and has little to do with pipelining or microcode. The trade off is just: you gonna have finite bits to encode shit, so if you move the loads and stores into their own instructions, you can have more registers.
Yes, it’s worth it in that you get more, highly engaged readers of your content with email signups. Some of them are web readers who read more because the reminders prompt them, but many are email readers who don’t really want to visit your website but want your content. It makes a lot of sense to offer a free subscription to someone instead of making them search for it.
There are also readers like you and me who look everywhere on a site to find what we want. They don’t need a pop-up and may resent it.
Of course you need to do the additional work of sending good email. That’s part of the appeal, that you’ve done additional work for the reader and are inviting them to enjoy more.
Why so much of our economy and society is driven by people asking other people to do things for them is a good question but above this particular consultant’s pay grade. ;)
$208k minimum salary does seem a little steep in order to justify hiring a foreign worker over an American. But, at least I like that startups are saying "it's too expensive" rather than "there's a talent shortage!" There's never been a "talent shortage." There's been a lack of incentive for said talent to join tech companies. Money is an easy way to make up for said lack of incentive, but companies don't want to open their wallets enough to get rid of the "talent shortage."
[ Disclaimer: GH employee but speaking independently & not representing the company in this message ]
You're mixing up controversies - there was a separate "feature" Grubhub did years ago where grubhub would stand up online presence for restaurants to bring in web search traffic (branded websites, search results on grubhub.com, etc) and list a grubhub phone number instead of the real phone number so that grubhub could collect comission on the orderflow that they're raking in for the restaurants. These were partnered restaurants, so they were signing up for this and could opt out of any of these services, in theory anyways I wasn't part of this so I have no idea if it's really that easy to opt out
Separately, a practice pioneered by ubereats and doordash, "Place and Pay" is a new thing in the past 2-3 years where Grubhub will just list a bunch of restaurants without them asking for it ("non-partnered"), and when you place an order online the driver will go in and order takeout, then carry it to you. The restaurant can opt out of this, but they never asked for the service in the first place so it's kinda shitty. That's what this article is about.
Grubhub was against place and pay at first, when UberEats and Doordash began doing it (not because Grubhub is selfless but because partnered restaurants are way more profitable), but resisting place and pay turned out to be a recipe for losing market share so that's no longer the case.
A more general comment because I see these services popping up on here from time to time: You’re not an alternative to IFTTT or Zapier unless you have a comparable GUI, full stop.
I would love to see an alternative to these services that could be self-hosted, but the reason why these services are useful for most people is because they have a simple web-based interface, even compared to something like Yahoo Pipes. This opens up their capabilities to non-technical users. If you’re asking people to edit configuration files, you’ve already lost them, unfortunately.
If someone can do that, that’s where the opportunity lies for an open-source alternative to Zapier or IFTTT.
FreeCAD already uses it, SolveSpace integration is in work. I know nothing about OpenSCAD and PythonCAD. There is also a very new CAD in planning from Argentina, which name I forgot, which uses gambas, a VBA clone in Linux. which will use LibreDWG.
Yeah when I heard about this I instantly thought of game engines, but it makes total sense for HFT too.
"Modern C++", with all its constant little mallocs and frees is so awful for anything that requires ultra low latency
That's a poor (and partially false) defense for Google's handling of the Bootloop of Death, for the following reasons:
I bought Google's flagship handset online from the Google Store. It was branded as the "Google Nexus 6P", it was shipped to me by Google, and it bricked itself while booting after a Google-supplied Android update. Google provided and managed the warranty. I had one warranty claim with them prior to my phone bricking itself, handled entirely by Google; Huawei was not involved in that claim at all.
My relationship as a consumer of a Google product is with Google, not with its contract manufacturer.
The Bootloop of Death affected multiple SKUs across different Nexus models. The 5X was manufactured by LG for Google, and the 6P was manufactured by Huawei for Google. The Bootloop of Death was present on both models.
If Google has a quarrel with Huawei, LG, or another contract manufacturer over the cost of managing a defect, that's their prerogative. However, I am not party to that quarrel. I am just a customer who bought Google's flagship handset.
Google suggested that I contact the nearest Huawei service center...in mainland China. The company took an arrogant "who, me?" attitude toward its flagship handset, and tried to weasel its way out of dealing with valid customer complaints, rather than taking some semblance of responsibility for an obvious problem.
> The Nexus phones were these shared branding between Google and the makers (LG, HTC, whoever)
This is not true. The Nexus 6P was marketed by Google, not in a shared manner. You're thinking of the Nexus 6, a Motorola-made device that preceded the 6P and was offered in some markets without Google branding.
> With the Pixel line, Google fully owns support of the devices, which makes it a bit easier for Google to deal with customer support issues like this.
Google fully owned support for the Nexus 6P until the bootloop issue came around, at which point Google changed its policies. Also, Pixel devices have been manufactured by competing handset manufacturers for Google (Pixel 2 phones were manufactured by HTC and LG).
The result of my experience is that I will never, so long as I live, ever buy another Google hardware product. Not a single one. I will not buy a Nest Thermostat. I will not buy a Chromecast. If my best friend has a lapse in judgment and makes the mistake of buying a Pixelbook, I will wait for him to leave it on the couch, unintentionally sit on it, and buy him a 16" Macbook Pro as a replacement -- apologizing profusely all the while, unlike Google support which was ostensibly trained not to use the phrase, "I'm sorry." Every time someone tries to defend Google for its handling of the Nexus Bootloop of Death fiasco, I add twenty years to the length of time that the trustees of my estate will prohibit my assets from being used to buy Google hardware products after I am dead and gone.
Calling a democrat that won't even pretend to support blue team freedoms the "worst democrat" makes a lot of sense.
What is called "centrist" is nowhere near the center, but is actually straight up authoritarianism. If you look at both the blue team's and red team's grassroots messages, individuals are not happy with how much control the government exerts over us. Each political team markets a half-libertarian message and lures individual voters in by focusing on those gripes. They then channel their supporters' energy into going after the "other team", and "compromise" by enacting the fully authoritarian policies their sponsors paid for.
> “Firms intend to hire these people back,” he said, referring to a recent survey of businesses by the Federal Reserve Bank of Atlanta. “But we know from the past that these aspirations often don’t turn out to be true.”
What past scenarios can we base these conclusions on? Nothing like this has ever happened in the modern economy. In the past when we’ve had this kind of job loss, there was significant capital destruction, e.g. bankruptcies of farms and loss of production from the dust bowl, or fundamental devaluation of assets, e.g. property being worth less than previously thought. Here, at least for the moment, GDP is down simply because people have stopped working. It’s not clear the productive capacity of the economy has decreased.
Honestly, I have no idea what will happen. But I think it’s probably not correct to try and compare this to previous recessions.
I think UE and Unity has complete different markets. Unity is focused on small mobile game developers, those small shops don’t have expertise to work with UE C++ source code and most of them are new grads themselves.
I’m not sure what is the overall strategy of Unity but I don’t believe they care much about the PC/Console space and frankly at this point I don’t believe they will ever manage to capture it from UE.
No offense to the people who built this, but sharing your username and password with random packages on the internet seems like a bad idea, especially for finance apps.
Alex Jones being kicked off those services isn't the same thing. He was spreading major misinformation and targeted harassment at innocent people that were involved in a tragedy. He wasn't "conspired" against. They just told him to go host his hate somewhere else.
And stop with these "censorship" BS. Alex Jones has every right to start his own network if he wants and put anything on it. There's nothing stopping him from doing it. But there is also zero reason why another private company has to be forced to carry something they don't want to. Free speech doesn't mean everyone is forced to listen to that speech. Why not say that CBS/NBC/ABC/PBS are also "conspiring" against him too because they don't carry his show? OMG, Nickelodeon doesn't carry Alex Jones! They're censoring him!
How's async looking in Rust these days? About a year ago I wrote one service that's in production. I ended up doing a lot of the futures stuff by hand. Never really understood how the error mapping/conversions worked, and usually just fiddled with them until it compiled. I remember the docs being decent, but there wasn't a single book/site that had everything in a comprehensive and approachable manner. In spite of all that, the service has chugged along pretty nicely.
Ultimately I've just been more productive in Go for the time being, but I remember definitely see the potential down the road for great things.
Has async/await permeated the ecosystem? Is the book more fleshed out?
