343 karma · joined November 10, 2019
If you spend $200 on a VR headset, expect to get what you pay for
* The compiler.
* The type system.
* The core library.
Google sucks.
Put those two things together, and not surprisingly, the result is awful.
In any substantial language, the "lexer" and "parser" represent less than 1% of the work of implementing the language. In the Ecstasy (xtclang) project, writing the lexer and parser (and then bootstrapping them both in the Ecstasy language) took less than 4 person weeks, out of 750+ (and counting) person weeks spent implementing the language.
As with many others here, I pay a great deal of taxes, by any measure. I do not want my contribution (_our_ contributions) to be used to hurt people for the purpose of hurting people.
This is not a "flamewar thing". DeSantis chose to hurt people to accrue power to himself. Given the gifts and the fortune that we have inherited, if we cannot speak truth to power, then it would be better had we never been born.
Sorry, not sorry?
Yes. That makes sense to me.
What's the downside?
It is frustrating to be sending piles of money to these states every year, which they then waste on political stunts like flying legal immigrants to other states, instead of taking care of their citizens, or maybe investing in climate hardening.
And then they're completely unprepared for cold weather, hot weather, wet weather, dry weather, ... and say things like "Nobody knew ___ could be so complicated."
I really don't mind my tax dollars going to these states, but I don't want my tax dollars to be wasted, or worse yet, spent to hurt people on purpose.
* Adobe has a subscription model in place, with a large number of customers
* Adobe has bundles already, and this could allow them to expand some of those bundles or introduce new bundles
* Adobe may be able to (successfully) charge more for the same product, because they're a bigger company that charges more already for other stuff
I list these items because I got to witness an acquisition of a product company first hand (I was the founder and CEO) and the acquiring company was able to derive on the order of 10x revenue from the acquired product, vis-a-vis the trailing 12 months before acquisition.
$20 billion is a steep price, but if the product fills an important gap, if aggregate demand (and fit with the other products) is strong, and if Adobe can drive sales effectively, then it is possible that the acquisition could pay off quickly.
On the other hand, I've seen quite a few failed acquisitions that will never pay for themselves; nothing here is a given.
It's an acronym used by Trump cultists to describe people who don't want to belong to their cult.
That is a very quaint thought.
SMH. This really is as stupid as it sounds.
What a disaster.
* Java-like language
* immutable “objects”/values are the first-class citizens
* method implementations can use local, mutable semantics (including mutable captures)
But on top of that, neither the slab allocator nor the GC are free. They're fast, and they're very good, but they also make heavy use of the memory bus, thus competing heavily with the cache-thrashing already being caused by the objects being allocated.
This is why in Java, on a heavily threaded and heavily loaded process, you can see that the CPU cores are far from 100% utilization, but yet there's no blocked threads (and more threads than cores). In other words, once the memory bus saturates, the effective throughput of the CPU drops off and the system cannot make full use of the processing power available.
The relative cost of memory access has gone up 2 orders of magnitude in the past 25 years, and that's before the bus becomes saturated. When the bus is saturated, it can go up dramatically from there (see: queue theory).
Some people will think that is a compliment.
Some people will recognize that as an insult.
How do you know that it is DisplayPort pass-through?
From what I've seen, if it's going through a USB-C hub, there is almost zero chance that it is DisplayPort pass-through, although such a thing is possible to implement, in theory.
As I said, justice means equal application of the law, and threats of violence and calls to violence are never OK, even when they are "on your side". It doesn't matter if you are calling for the killing of trans people, or the killing of people who are mean to trans people; calls for violence are wrong, and threats of violence are wrong. I hope that we can at least agree on this one thing.
And frankly, shame on Twitter if they did not take quick action on the posts that you linked to. And FWIW, the first post (an obvious threat) has had its account deleted, the second post was neither a threat nor a call to violence, the third post (an obvious call to violence) has been deleted, but the account remains (but is dormant), etc. So it appears that something _was_ done, but I know neither by whom it was done, nor when it was done.
I know that I'm going to regret stepping in this pile of community dog poo, but ...
The simple idea behind "the rule of law" and the concept of "justice" is that it applies equally to all. Regardless of what someone claims to "support" or "oppose" online, death threats are illegal (and sometimes deadly) and should be dealt with accordingly.
I am personally unaware of "trans people and their advocates" having "free reign everywhere on the internet to harass, doxx, send death threats, call for the murder of JK Rowling". As Carl Sagan said, "Extraordinary claims require extraordinary evidence"; in the absence of such evidence, which your post is, your claims are inflammatory, at best. Were there an option to report your comment (or were I intelligent enough to know how that option worked), I would have done so.
I know that I should not have to spell this out, but it is not OK to threaten people's lives. This, regardless of whether (i) you are trans, (ii) you support trans people, (iii) you hate trans people, or (iv) none of the above.
/s
(Sorry, I initially forgot the sarcasm indicator.)
I feel like we've lost something special here ...
Several years ago, fabs started naming each next-gen process with a smaller number of nanometers, even if the process size didn't change. It's just marketing now.
Especially the DBAD comment.