Raising rates does Absolutely Nothing to undo the tariffs or bringing the price down. Fed is not a blind machine.
2,450 karma · joined March 26, 2011
Raising rates does Absolutely Nothing to undo the tariffs or bringing the price down. Fed is not a blind machine.
My understanding so far based on buried comments is: other countries have tariffs on individual products they're historically good at manufacturing and they want to retain it. e.g. Milk in the Nordics, Cars in Japan and EU, Bikes in India, etc.
keyword: "selective to retain"
US is applying it across the board blindly, not to retain something that's existing, but what appears to be a blind hope of starting everything from scratch.
Buried comments say "strategy" is lacking, because these tariffs also apply on the very raw materials needed to start from scratch. The policy does not intelligently select and separate items by their current or future use to the US industry.
There is a prediction that this blunt hammer will not yield to a more productive situation, in couple of years it would only have to be quietly rolled back and strategic thinking would have to be re-applied.
The counter-counter argument is, maybe a real strategy is being worked upon, and this blunt hammer is just a leverage tool. But so far there are no concrete signals of strategic thinking, so it's currently perceived as "let's keep turning one knob after another". The lack of accompanying software updates, calculations, projections, personnel planning, etc all contribute to the notion that there is no strategy.
And at this point, it devolves into emotion and personality, which is better to stay away from.
A 200-300kb "bloated" single page app which does the job of a 10MB "minimalistic" downloaded store app – is IMHO pretty incredible. It's doing the same work at nearly 1/50th the size, all else being similar (externally loaded images and stuff). Heck, even a 1MB page load size is still 1/10th smaller.
Sure, it can be argued that the browser does most of the heavylifting. The same can be said of Android or iOS too, definitely the OS offers _even more_ heavylifting than the browser.
He exited and correctly disclosed himself as a victim of being unknowingly added. This is exactly what anyone who values the rest of their life should do.
That's not what the title says though. It says "research over revenue" not only research no revenue.
I found the title misleading for a different reason: the "unlike silicon valley" part. IMHO SV couldn't care less about revenue than innovation, experimentation and ultimately valuation. Stock prices have been long detached from revenue multiples.
Here I am, in Germany, my kid goes to school by himself since second grade. Most of his classmates started to walk, bike, or take the train, bus or tram themselves at 3rd or 4th grade. Beyond 6th grade, it's considered a spoiled baby.
Super bizarre. We're a large Opsgenie customer. The Opsgenie website or mobile apps never showed any notice, not even as of now. The "Announcements" section in the mobile and web apps as I'm writing reads a feature announcement: "Coming soon: Simplified integration setup experience!"
Our customer relationship nor billing teams never received any communication.
Atlassian — we don't mind you sunsetting any product, that's fine. But honestly, your paying customers shouldn't get to know this from a blog post in social media, especially for an On-call emergency product.
I wouldn't trust any product from Atlassian after this fiasco.
Edit: Airpods also has a majority market share, so probably it's not the third in this list.
What about all the words that are not picked? That's for 2 years later, when they play the same game again.
Here's the last but least favorite part: beat employees into memorizing those words, have them graded against these words based on entirely subjective interpretations, and reward those who are good at playing this game.
Some people are just story tellers, not doers.
Then I look at the profile of the author of this blog. Yeah, makes sense.
There is no point in differentiating this like "ah it's on a bigger scale" or something. It's still just pretty basic.
IMHO the true limitations of RDBMS are not about usage, but scaling: Multi master across simple zones, High availability, Partitioning.
(IMHO it comes from ACID compliance, so I don't know if it's even solveable natively)
Being mindful of the never-ending-nirvana frontend spirit of churn, and after doing web development in VBScript, JS, JQuery, Mootools, Applets, Actionscript, YUI/Ext/Sencha, Backbone, Knockout, Angular1, Angular2, React, Vue1 – I'd say try Flutter. It's genuinely a breath of fresh air.
Except... Dart. If only Flutter was in Typescript it might have been a bit closer to nirvana. The Dart part is still keeping the frontend spirit of churn alive.
Literally every single decision they listed was to use any of the given tools in the absolute worst, incompetent way possible. I wouldn't trust them with a Lego toy set with this record.
The people who quit didn't quit merely out of burnout. They quit the stupidity of the managers running this s##tshow.
A lease has a time limit. A lock does not. Clearing stale locks manually is a PITA. I still assume, being a Web-scale contract, the lock would be automatically cleared if the browser is restarted or something. But honestly a lease makes users do better design from the get-go.
https://speakerdeck.com/cgriego/models-models-every-where?sl...
Yes, there are other factors such as bonded labor, indemnities and local laws taking precedence. But this is such an obvious abuse factor, it makes sense to remove it. Of all the ways to do it, whether it's paid lockers and so on – what the parent comment said is still a cheap way.
Just create a couple more for AI, one with training data, one without.
Holy grail thinking, finding "the one and only open" license instead of "an open" license, is in a sense anti-open.
Secondly, that's like asking cpu to do the job of a compiler. The compiler has one advantage over a cpu: it runs in a completely situation where memory and time do not matter. The cpu doesn't have the luxury of trading off memory or time.
> Firefox has continued supporting HTTP/2 push as this wasn't too large of an effort until recently. > However in the past few months we've encountered some webcompat bugs only affecting Firefox through HTTP/2 push
They are clearly saying that recently there has been bug report, and this blog post is to do exactly what you mentioned as other browsers do: reject H2 push and gracefully ignore it. There does not appear to be any hiding here.