Most of these programs require you to be able to clear the bureaucratic hurdles to be eligible for them; welfare reform in the '90s made many welfare programs temporary or added work requirements to them (like TANF, which is "temporary assistance for needy families). This continues today, with the Trump administration allowing states to add a work requirement for Medicaid, which in many cases would then make people ineligible for Medicaid as they would earn too much to qualify, but too little to get Obamacare subsidies for private insurance.
If you don't have a permanent address, up to date ID, and a bank account, and a job, many of these programs may not be available to you.
But I believe these counts do not include welfare programs other than those that give you cash (like Social Security benefits including disability). Other programs offer services or restricted forms of payment, which cannot be used for saving, for purchasing other things you might need like gas or transportation, and so on.
That makes no sense; you can't make "too little" to be subsidized. People making just over the MediCal threshold pay as little as $5/mo in CA, with the other $350-580 being subsidized (they aren't even limited to Bronze policies!).
This happened because the Supreme Court ruled that states couldn't be compelled to expand Medicaid to cover the gap, which the original legislation had depended on to make the plan work. So states which did not expand Medicaid have an income range in which you can't get Medicaid or Obamacare subsidies.
One thing to understand about the US is that it is actually a federation of states. Much of the day-to-day work happens at the state or local level, not at the federal level. Police, fire departments, emergency first responders mostly employed at that level, and when the federal government is involved, a lot of it is in doing some coordination between states, setting standards, funding for various programs, and so on. Even things like building interstate highways, which are funded by the federal government, are generally done by allocation to the state governments to actually construct them.
However, the military is entirely part of the federal government, as are many other organizations. In the case of not having a budget, the government is required to shut down all functions that are not essential for safety and security. So things like the military, the TSA, and so on can continue to function, but office workers doing jobs like allocating the funding for highway construction are furloughed, put on temporary unpaid leave from their jobs.
This is, of course, terrible for the efficient functioning of government; when the impasse is over, they will have to come back to their jobs and try to catch up. Oh, and in the time leading up to the shutdown, many of them would have been busy preparing for the shutdown, documenting which functions would be considered essential and thus able to continue during the shutdown; because the deadline was no surprise, and there had been many temporary funding bills leading up to this point, there was always a pretty high chance that this shutdown would happen.
Of course, this inefficiency plays well into the politics of one of the parties, who hold a religious belief that private enterprise is always more efficient than government, and so playing games like this that increase its inefficiency help to sell their case and get government functions sold off to private enterprise, who just so happen, in so many cases, to be some of the largest donors to campaigns of this particular party.
"Of course, this inefficiency plays well into the politics of one of the parties, who hold a religious belief that private enterprise is always more efficient than government"
Which is beyond ironic to anyone who's worked in the corporate world, but I guess that's for another thread.
This idea they have that private enterprise naturally evolves toward the most efficient system is laughable.
I've worked in both, I find bureaucracy is roughly proportional to the seriousness of the work. Serious work - Law, Healthcare, Finance etc are very bureaucratic regardless of whether it's the private or public sector.
Public sector can sometimes seem worse because there's less money sloshing round and people demand it isn't wasted, which effects a lot of bean counting.
There's also something to the notion that we want our regulatory bodies and government agencies to be slightly 'conservative', to avoid waste and avoid short-term folly. Our public institutions should live for generations, and have transparency and ethical demands placed upon them by the citizenry.
We could collectively decide to eliminate a lot of red tape in government, no problem. It's just the effect of unchecked, unsupervised, unaccountable governments that make us want that red tape in the first place. Todays Justification Paperwork is yesterdays front-page scandal...
In my native Norway, we let the public sector and private sector compete to perform public services. I can't say that I've ever seen that the private sector has a clear advantage, otherwise they would already have taken over running everything.
In fact I think I know of far more cases of private companies doing considerably worse job than what the public sector did.
My city recently switched to a private company for garbage collection e.g. It was an absolutely horrible mess. My home town had a care home for mentally ill people, that got taken over by a private company. They promised to run it cheaper than the government. Except they totally messed up everything. They lost a lot of talented people, who quit due to their poor management. Then they demanded to be paid more than the public solution had charged to do the same job.
So not only were they worse, they were also more expensive. Sure these are just anecdotes. But it puts a hole in the claim that the private sector is ALWAYS better. To disprove the notion of always you only need a single counter example.
I am not against private companies. Just let them compete on equal terms and prove that they can do the job better. Unfortunately our conservative government is often so ideologically tied to the idea of private always being better than they push for private sector solutions even when a company is not able to demonstrate that they do a better job.
In fact almost every case I've seen where a private company does the job cheaper, it is because they give their employees worse conditions and salaries, not because of smarter organization and management.
I can't say that I've ever seen that the private sector has a clear advantage, otherwise they would already have taken over running everything.
An entity that can rig the courts, the laws, and the regulations to its favor has an advantage.
Sure these are just anecdotes. But it puts a hole in the claim that the private sector is ALWAYS better.
Yeah, that's just magical thinking nonsense. You have to take the situation apart and look at what the incentives are. Economic libertarian woo is just as bad as alternative medicine woo. Markets aren't magic. They are a particular kind of distributed machine. It sounds like that mental hospital/home didn't have a competitive environment, or they couldn't have demanded more funding.
In fact almost every case I've seen where a private company does the job cheaper, it is because they give their employees worse conditions and salaries, not because of smarter organization and management.
In Washington state in the US, there were private DMV counters at Fred Meyer. AAA auto insurance can also do some of these functions. The customer experience is almost universally better at the private counters, because the private employees have incentives to make the customer experience pleasant, and the state employees have none. If a company can cheap out on its employees as compared to the state, and the level of service stays the same, then the market worked. If a company does that, and the level of service gets crappier, but the company doesn't face consequences, then the market has not worked. I bet, if you tried hard to prove the null hypothesis and looked for circumstances that would interfere with the market, you'd find them.
Yes. For one, they've obtained a position where you are forced to patronize them, even if you would choose to not utilize their services. For two, they generally get themselves excepted from local regulations (eg noise ordinances) for essentially convenience purposes.
Having said that, "privatized" trash collection creates its own type of shithole - whether it's a single vendor obtaining a city's exclusive contract for politicians' short-term balance sheet gains, or many competing services that result in visits by multiple trash trucks every single day.
I'm of belief that the inefficiency scales with internal organizational complexity, which roughly scales with size. Basically, the more people you need to involve for a typical step in a project, the less efficient you get. Government branches seem to be terribly inefficient, because even the smallest one is in fact responsible to a lot of people (other agencies, oversight bodies, politicians and, ultimately, the public).
I'm a business analyst and work with both private sector and government clients. From about a decade of analyzing how each type operates, I can tell you that the amount of bullshit that goes on in them is about the same level.
Sure, but the private sector has its own equivalent vehicles of waste, such as corporate executives getting paid insane salaries and bonuses even for average performance. You don’t get that in government because salaries are capped.
>This idea they have that private enterprise naturally evolves toward the most efficient system is laughable.
This is a straw-man, nobody claims that private enterprises are necessarily more efficient than government organisations. What is claimed, however, is that a free-market system invariably leads to better processes and products, compared to a government monopoly, because there is a competitive advantage in optimising overheads.
To suggest that government organisations are "often" or even "occasionally" more efficient than private organisations is quite chuckle-worthy.
>>Of course, this inefficiency plays well into the politics of one of the parties, who hold a religious belief that private enterprise is always more efficient than government, and so playing games like this that increase its inefficiency help to sell their case and get government functions sold off to private enterprise, who just so happen, in so many cases, to be some of the largest donors to campaigns of this particular party.
One party believes 92% of this and the other party believes 83% of this statement, for any non-American reading this.
FYI this is a great neutral explanation up until the last paragraph, which is politically charged. This attempts to imply the Republican party sought the shutdown. In fact, the shutdown was caused by the Democratic party not voting for the Continuing Resolution (pseudo-budget). 60 Senate votes are required, but the majority party (Republicans) only has 51. It's a big slimy ball of politics all-around.
Also, more on point, many government entities have "carry-forward" funds which are available during a shutdown. In 2013 the Executive Branch (Democrat president) discouraged the use of these funds. The current admin is encouraging their use to ensure as little disruption as possible.
Clanan, to my knowledge this is ALL Trump and the republican's fault. Until 3 weeks ago they could have passed anything they wanted. It is just because they wasted time and Trump sabotaged everything the republicans came up with that so much time passed that they reached a stage where a 60 senate vote was needed.
You can't blame this on democrats when republicans could have handled this exclusively themselves and had ample time to do so.
This is simply a reflection of the chaos that is the Trump administration.
It is ironic to think of how I told Trump voters before the election, that if you vote on that man you will get noting but grid lock politics, because he is not a uniter. He is not a man who seeks cooperation and common ground.
I got laughed at for this, with Trump supporters telling me they didn't need democrats for anything because they controlled both houses.
I guess it is my turn to laugh then. I great irony that they manage to get themselves into this mess. The democrats didn't even have to lift a finger.
Citations are far more helpful than ranting. If you want a productive conversation, you should provide some. Democratic leaders have made the current budget/CR about DACA, which was not relevant to it. (Ironic because they're in favor of everything in the CR, but they voted against it anyway!) Here's House minority leader Pelosi promising to block any funding that does not include DACA [0]. Yes, the Trump admin could have avoided the shutdown by giving in to minority demands, but that doesn't mean they're at fault, logically.
As for opinions, my political golden rule is "never trust a politician". We're veering far off-topic, though.
Edit: as further evidence of the cause of the shutdown, Senate Minority Leader Schumer just caved. The shutdown was a political gamble for both sides; I'm assuming internal Democrat polling found that they were receiving the most blame. Continuing the disruption would be disastrous. (Obvious, considering they effectively blocked the CHIP children's health insurance.)
Government is only funded through Feb. 8 and this reauthorizes the Children’s Health Insurance Program for six years.
So, they got something they wanted all for keeping the government operating for another 2.5 weeks. I would call it a solid democrat win.
Also republicans can pass 1 bill per year without the risk of filibuster and they used/wasted it on their tax bill. Thus, any government shutdown is arguably 100% on them.
You're projecting your politics onto the events. The CR already contained CHIP, and the majority already promised a debate on DACA/immigration back in December. The Democrat leadership promised a shutdown if DACA was not added to the budget/CR. They shutdown, but then reversed almost immediately without DACA being added. No idea how that can be labeled a "solid democrat win" without some severe rationalization.
> Thus, any government shutdown is arguably 100% on them.
Under this logic, all outcomes can be blamed on the majority party in all situations, because tool X was used on Y instead of Z. In a theoretical situation where a supermajority vote fails 59-41, isn't it more logical to blame the failure on the 41 opponents rather than the 59 proponents?
Sure, blame them too. If a bill fails, blame everyone who voted against it. I didn't mean to imply otherwise.
Of course, then you have a situation where politicians (on both sides) will grandstand if the outcome is already decided. For example, if a CR is guaranteed to fail, a moderate Republican will vote against it to appease his base. But if his was the deciding vote, he would vote to pass it to appease his party. Politics...
You say, now. After mentioning how Democrats are to blame at least eight separate times in this thread, and mentioning how Republicans are also to blame... none, until this comment.
Senate Democrats initiated the shutdown by opposing the continuing resolution. You can blame Trump if you want, but only in the sense that you could say it's his fault for not giving the Senate Democrats what they wanted.
Tea Party types found rationalizations for why the 2013 shutdown led by Cruz was really Obama's fault, so I'm not surprised #resistance types are blaming Trump.
What I don't understand is all this fuss about the Democrats having to vote to pay for Trump's wall, after all he promised that Mexico would pay for that, it shouldn't be a sticking point at all
Why could they pass anything up until 3 weeks ago? I though filibustering meant the senate always needed 60 votes if the opposing party wants to block the legislation.
They could have used the budget reconciliation process to bypass the filibuster. Instead they used their one opportunity this year to do that to get the tax bill passed. If they hadn't insisted on forcing through a (historically unpopular) tax bill, they could have passed a funding bill over any Democratic opposition.
As I recall from the last shutdown, Congress usually passes an apology bill to pay back-wages for the furloughed workers. In theory, it's unpaid time off, but in practice, they get made whole and it becomes a free (but potentially angsty) vacation.
Ah, you're right. I didn't recall whether they had been paid for that.
Either way, it's fairly inefficient; either they were paid for doing no work, or they were not paid and may leave for better jobs or morale destroyed due to that.
Beyond the pay itself is also the financial anguish and unnecessary work the employees might have to go through if there is a missed car-payment or loan-payment or down-payment on a house... This creates meaningless productivity loss, with oodles of meaningless lost productivity required to make up for the original loss, to the glorious benefit of destroying morale and scaring away talent...
10/10 federal policy. #ShootFootNow #AskQuestionsLater
IMHO, states should be prepared for federal governments being "shutdown" or dissolved. What we call shutdowns are not real shut downs. Military doesn't go on leave. They still do their same job. Many key workers do their same jobs as well. Some workers end up staying home and then later are usually paid for the time they missed at work anyway. #FreeVacation
It is a contrived emergency so the political parties can try to increase pressure to get pork through that they would not have otherwise in order to get the votes high enough to end the BS.
IMHO, the federal government should be entirely dissolved and the states should have a more loose confederation like the EU has. Federal law and over spending have gone too far. By overspending, I mean how the DoD decided to spend billions that it was not given by Congress. I don't mean any liberal vs conservative notion of how government should spend.
I know this is a pipe dream, but one way it could happen is through a "shutdown" that never stops.
chisleu I've contemplated this as well. I don't really believe in big political unions. However there are major practical problems dissolving a union which needs to be addressed, which people who favor dissolving a union seldom address.
It is very hard to have open borders between states if there is no federal authority. It is also hard for a state to run their own economic policy without their own currency and central bank.
Already American states struggle with running different welfare policies. You see how red states e.g. a freeloading on blue state welfare programs, by dumping their poor people in blue states and enticing companies created in innovative states like Calefornia by luring them with low taxes.
I personally think it would be nice if we could have a wide selection of countries and states following completely different policies. It is good with experimentation and trying new things. In practice however this is difficult, as somebody can just freeload on everybody elses work by creating a tax paradise.
What I don't understand is this: why not just change the process so that unless there is any change in funding decided politically, funding always continues as-is?
The whole setup is stupid, due to a chain of constitutional oddities. There's no distinction between budget votes and other kinds of votes. Most other systems, Westminster-style or otherwise, have a process which results in either a budget being passed or a fresh election being held which should result in a majority capable of passing one.
The US system has elevated a denial of service attack (filibuster) to the status of important democratic ritual. This doesn't help either.
("Funding continues as-is" may be rendered impossible by external factors, as in the Greek budget crisis.)
It is impossible for this not to be a political topic and I probably shouldn’t be even discussing it here, but whatever.
What would be the reasonable thing for the democrats to do right now? They weren’t allowed to see the tax bill. That’s what happens when something has the 51 republicans and it can’t be filibustered in the current environment.
Further, the republicans haven’t even brought a bill forward to be filibustered likely because they don’t have the votes in their own party.
I’m fairly centrist for this site but the republicans controlling every part of the government as well as already using their reconciliation power and blaming the democrats is so shockingly perverse in its cinycism. That’s before you even take into account the duplicity on DACA that has broad bipartisan support up to a meeting with the president last week.
Neither morally or strategically should the democrats budge on this.
Except they are hurting tons of people in the US in exchange for strategy. That's simply not right.
And of all issues DACA? It's important to some people, but as a national topic it's pretty minor.
> What would be the reasonable thing for the democrats to do right now?
Realize they are weak and accept it. Then take the offer they were given and do the best they can. But don't hurt unrelated people in the US to try to increase their own strength.
As a national issue, deporting people who should by rights be citizens and have known no other country than ours, many of whom are parents of actual American citizens, children, citizens, who might not even know Spanish, that's a minor issue?
In comparative terms it's minor: 35 million enrolled in CHIP [0] (shutdown) vs. 3.5 million DACA. Hopefully all would agree that neither is minor from a moral standpoint.
... Until they did? Your comment is true of all bills and all proposals. "Party X was free to vote on it, they chose not to. Until they chose to." Furthermore, the minority had promised to veto all funding unless DACA was included, at all times. Regardless, the above comment was simply pointing out the difference in terms of magnitude.
Maybe the simple reading of the statement is true of everything, but what’s unique here is that it was deliberately held up so it could be used as a bludgeon during the shutdown negotiations.
Especially egregious was the fact that it had broad bipartisan support, and had been scored by the CBO to save money. The health and welfare of children was used as a political bludgeon.
The 51 seat party should simply out forward a bill that can be accepted by 60 seats. If they fail, they should take 100% responsibility. Republicans have to concede that those last 9 seats are democrat seats and the power of those seats is (perhaps unfairly) almost as big as the 51 first seats, but the responsibility still lies with the majority to govern.
You know, like I'm sure you wanted the Republicans to do under Cruz in 2013?
Shame on the Democrats for opposing the Republican party, as the Republican party did the last eight years. They should just "realize they're weak and accept it [and do what they're told]".
The sad thing about this is that you most likely you think your perspective is eminently objective and unbiased.
I personally, was totally against the tax cut after reading about it in the media.
Then it actually passed and the media (yup, that same media) put out some calculators. I played with those, and realized I was seriously mislead.
Wait another month, when people will get higher paychecks, and see if it's still unpopular.
I really wish the media would stop telling me how to think. Just tell me what happened. Leave out the reactions, and quotes from "other people" telling me what I should think about a topic.
Best I can do right now is read opposing media outlets and contrast them, but it's hard to do.
So? The survey is older than the present. The comments I've seen online and in person show that people actually do support it, which will only increase once higher paychecks arrive.
Are you? I don’t think the popularity of the tax cut is terribly relevant, although its unpopularity makes this cock-up worse. You felt it was worth correcting, but you can’t back it up with anything more than anecdotes or guesswork. So what’s the point of arguing?
This gives a much greater ability to iterate rapidly on new layout and styling details, polyfill for specifications that aren't widely implemented yet, and hook into some parts of the browser stack that you previously just had to use as is and trust that if you need a new feature, it would eventually be specified and/or implemented.
I think this article does the best job of explaining the whole effort:
I wonder if there's anything in the Houdini project that will let me fix this. This paint api is useless to me since it doesn't give me the original contents of the dom being styled (so I would need to redraw the text, style it and layout it on my own). The solution I ended up with is using svg filters: https://www.smashingmagazine.com/2015/05/why-the-svg-filter-.... But a unified solution to customizing CSS without needing to call it a hack would be nice.
You used to be able to buy Lemote Yeeloong notebooks, which in addition to having Loongsong processors had completely free software BIOS, making them one of the only RMS approved pieces of hardware. But I'm not seeing those readily available any longer.
IA-64 (https://en.wikipedia.org/wiki/IA-64#Architecture) already exists, with its explicitly parallel instruction set, which leaves branch prediction and speculative execution up to the software. So you can still get many of the performance benefits, but it's under control of the software, giving a lot more flexibility for being able to mitigate or eliminate these kinds of issues.
I think that it was probably introduced ahead of its time, and targeted at the wrong markets, but it's kind of sad that with the Spectre vulnerabilities, we don't have any way of comprehensively addressing it in software without jumping through a lot of hoops and applying microcode updates.
IA-64 was a dumpster fire. The halting problem is unsolvable. You can't schedule branch prediction absolutely. You have to have information about the current running program. Branch prediction, instruction re-ordering, and speculative execution are to hardware what a JIT is to software (roughly speaking).
Unfortunately, from a security perspective, moving those things to software doesn't make the vulnerability go away. You can have the same vulnerabilities in your software implementation.
From a performance perspective, we have no general solution to parallelizing a serial program. GPUs used to be VLIW. AMD switched from VLIW-5 to VLIW-4 because the average width was only ~3.5 (Nvidia had switched from VLIW to SIMD long before this). Today, Nvidia and AMD both use a MIMD threaded approach to execute on SIMD units.
Later-generation Itanium chips wound up including branch predictors and speculative execution. From what I understand, under the hood, they were normal RISC-style processors (like all the x86 micro-arch are today). Just ignore the VLIW and run one set at a time serially with the ILP hardware optimizing as it goes.
In today's programs, the programmer specifies data-level parallelism where possible (and if necessary, re-adjusts the code so the compiler heuristics recognize it as optimizable). The compiler then tries its best to detect the parallel data and use SIMD and organize instructions so that the parallelizable ones are closer together (so they fit in the CPU reorder buffer). When they hit the CPU, it examines the code as it runs to optimize speculative execution and uses the reorder buffer to make efficient use of its computation units (load, store, ALU, FPU, SIMD, etc). You move from explicit to implicit-ish (you know that putting similar instructions will optimize in all modern processors), but don't have the drawbacks of noop code bloat or having to compile different code when someone changes from VLIW-2 to VLIW-3 code.
The unsolvability of the halting problems means that it is impossible to have a general algorithm that makes non-trivial statements about the behavior of a given program.
In the context of IA-64, that means that generally, the compiler will not be able to determine when it's save to use parallelism. We can only program it to use parallelism in a bunch of special cases for which we think it will be safe.
Given that simias originally asked for a simpler platform that we can trust in more, this seems to be a pretty strong argument that IA-64 is not that architecture.
If you're not only concerned about bugs but also about people inserting backdoors into your hardware it's not enough to have access to the architecture design, you want to be able to publicly audit and review the entire manufacturing process (to make sure that the design you audited is actually the one etched on the silicon). I doubt Intel & friends would open their high-end fabs to public scrutiny so I think you'd have to use older technology available "in the open". For this reason alone I don't think a truly open processor could compete directly performance-wise with the current high-end CPUs regardless of architectural choices.
If you're looking for relatively high and deterministic performance maybe Project Denver, the descendant of the Transmeta's Efficeon, would be a better choice? Of course the binary translation has tons of potential for introducing bugs but since it has an exposed pipeline the translation software would have an easier time guaranteeing you wouldn't run afoul of Specter. NVidia's incarnation seems about as fast as an A57 which isn't great but isn't peanuts either.
I think this is overlooking how unpopular IA64 was.
"Leaves branch prediction and speculative execution up to the software" means that in practice you need to either use the Intel compilers or hand-optimise your software to get the benefits, while simply recompiling your legacy software with GCC or LLVM ends up being disappointingly slow.
Oh, yeah, I'm aware of many of the reasons that IA64 failed.
Intel could have solved this problem by contributing to GCC and LLVM instead of keeping their optimizations proprietary. Then they would also be more easily auditable as well.
> instead of keeping their optimizations proprietary
There were no magic secret optimizations to release. It just straight up did not work. They had to add back dynamic branch prediction, and even then the load store latency was such trash that they had to put ginormous L3 caches on it to get even close to reasonable performance.
That's fair. I have never worked with them, so I don't know the precise details; but one of the big complaints I've heard was that compilers weren't ready for them yet, while these days there's now a larger field of open source compilers and has been a lot more research in parallelism.
Yeah, compilers today are no better. We found the limits of statically scheduled parallelism pretty fast. On code that uses static scheduling, a modern OoO processor can easily duplicate what IA64 was capable of (and a pipelined loop using AVX will utterly smoke it), while being far better at all the stuff IA64 failed at.
One big problem was the epic power consumption of the Itanic CPUs.
I remember going to a corporate presentation by Intel about the revolutionary CPU architecture. They had to turn the machine off because the cooling fan was making so much noise we couldn't hear the speaker.
And this at precisely the wrong moment in history, as mobile devices, with their stringent power consumption constraints, were becoming popular.
You're giving up on a ton of performance by dropping OoOE.
In particular, you end up losing the ability to avoid stalling on cache misses, and the memory wall becomes an increasingly gigantic problem even as Moore's Law progresses.
No, SMT techniques only help with throughput, not single threaded execution latency. Furthermore, if you have no OoO, then it's very likely that both threads will suffer a cache miss. Plus the overhead of SMT is very similar to just having two cores. Modern CPUs reuse much of their OoO circuitry for SMT, removing OoO means that SMT has greater relative overhead. (I can dig up the relevant papers if anyone's interested)
We don't need to give up on performance, even with low-performance RISC-V chips. What we need is a new architecture which takes advantage of low-speed multicore processors. If it is possible to produce thousand-core RISC-V chips [1] then any core could be assigned a single thread - which implies that there is no need for a complex multitasking OS.
[1] Towards Thousand-Core RISC-V Shared Memory Systems (PDF)
To get into trouble you have to be able to resolve one load and launch a new dependent one before the second load is quashed by the branch resolution. There exist in order pipelines that allow that, the Cortex-A8 for example, but they're pretty rare.
I'm just pointing out that Itanium had dynamic/hardware branch prediction and it's not necessarily immune to Spectre type exploits. As you mentioned, there are in-order scoreboarded pipelines that allow things like that, so dodging OoOE is not necessarily a perfect panacea.
I'm not sure exactly what would have been the right markets, but I think that something where legacy compatibility is less important and being open to experimentation and new software designs is more important. So, things like consoles (going up against things like the Cell processor), HPC, or maybe even the embedded space (tablets, etc), rather than trying to use it for the enterprise market as Intel and HP did, where running legacy pre-compiled applications is a really important use case.
Game developers are not at all open to experimentation, only adopting new languages or architectures when vendors force them to move forward.
PS3 with Cell would have been a failure had Sony not eventually caved in, and released a PS3 SDK that made most of the work Sony was initially expecting devs to do, regarding low level programming.
Avid Media Composer, one of the most popular non-linear video editors in the industry, does a stat of every piece of media referenced in every project you have open when you change focus from another application back to Avid Media Composer.
Since I work on network attached storage for video editing, I'm acutely aware of how much slowing down a few simple syscalls by just a little bit can be for certain very commonly used applications on macOS.
> I'm acutely aware of how much slowing down a few simple syscalls by just a little bit
I'm going to go out on a limb here and say that a NAS isn't slowing things down "just a little bit". It'll be more on the order of a million times slower, for those operations.
Syscalls are complex beasts, the patches for Meltdown only affect the bit where you transition between userspace and kernel space - this a static cost. Thus, when Avid Media Composer stats a few hundred files on a NAS far, far away from your CPU, the performance cost these patches incur will be negligible.
I would not expect that use case to be affected much. Network latency is too large, relatively speaking, and I don’t think that is “syscall heavy”, even if it does a thousand stat calls.
> Why not use a statically typed language for such a large code-base? Is this done by purpose, or did they end up with a million lines of Python code and are looking for ways to make the maintenance easier?
Being in a similar (though much smaller scale) situation ourselves, I suspect your latter suggestion is the answer; they wound up with a large amount of Python code due to expediency (Python is good at quickly getting things done), and are now finding the code base quite hard to maintain.
Something to remember is that as of 10 years ago, statically typed languages consisted of C (for some definition of "statically typed"), C++ (complicated and cumbersome, and didn't yet have widespread availability of "modern" C++ features), Java (cumbersome, heavyweight, lots of missing opportunities for abstraction back then), C# (heavily tied into the Microsoft ecosystem, not yet open source), and a bunch of weird academic languages that required tutorials about burritos to learn (ML, Haskell, etc).
While statically typed languages like C, C++, and Java were the mainstream languages of the 90s, C was too limited for a lot of people, C++ and Java too cumbersome to use, and so lightweight dynamically typed languages like Perl, Python, PHP, Ruby, and JavaScript picked up a lot of steam due to how much easier to pick up and more productive many programmers found themselves in those languages. But now we have large, fairly un-maintainable code bases in these languages, and people are realizing the value of static typing, in part due to the maintenance hassle and in part due to newer, more expressive and accessible statically typed languages being available (Elm, Rust, TypeScript, Scala, Go, Kotlin, as well as improvements to C++, Java, and C#).
But that leaves all of these old codebases, that are hard to maintain. Rather than doing a complete rewrite, adding static typing capabilities that can be applied to existing codebases is a way to make them more maintainable without spending all of the time of a complete rewrite and having everyone have to spend all of the time learning the new language while still maintaining the old codebase.
Also, these old code bases can now be fairly easily and optionally retrofitted using modern Python's support for type hints and tools like mypy and now MonkeyType. So people can continue using their existing code base and the vast Python ecosystem, with the added benefit of type checking where appropriate.
I've been considering doing a static/semi-static blog system which just notifies the user of discussions on referring sites, and makes it easy to link to and excerpt interesting discussion. Possibly even gives an easy way to submit links to start discussion on preferred sites.
That way, everything displayed on your blog is explicitly added there by the author, but once an interesting discussion has started you can easily direct users to it and they can participate under moderation rules of whatever forum that is.
I'd consider myself an expert on Git, and I use a GUI of sorts for the vast majority of my Git work: Magit in Emacs.
It has many of the advantages that you describe; makes it easier to get an overview of what's going on, makes it easier to stage individual files, folder, lines of code, hunks, etc.
There are a couple of cases in which I need to fall back to the Git command line, but it's not very often, and I do find it substantially improves my life.
If you don't have a permanent address, up to date ID, and a bank account, and a job, many of these programs may not be available to you.
But I believe these counts do not include welfare programs other than those that give you cash (like Social Security benefits including disability). Other programs offer services or restricted forms of payment, which cannot be used for saving, for purchasing other things you might need like gas or transportation, and so on.