... no.

As mentioned above, other countries realize that free/inexpensive higher education is actually an investment in their citizens and in their country's futures.

But i the grand tradition of the American “free market,” the U.S. once again proves that if there’s a way to squeeze its own citizens for profit, it’ll find it.

Other countries invest in people; we just invoice them and call it freedom, leaving generations shackled to long-term debt.

Other countries realize that free/inexpensive higher education is actually an investment in their citizens and in their country's futures.

Truth. Ever notice how every single one of the politico's who've been railing against "elitists" and who continually warn us against the dangers of "liberal" colleges all have their own advanced degrees?

Trump graduated from the Ivy League University of Pennsylvania and from the Wharton School of Business. Marco Rubio graduated from the University of Florida and the University of Miami Law School. Jeb Bush? University of Texas. Rand Paul? Baylor and Duke. Tom Cotton attended Harvard and Harvard Law, and Ted Cruz hails from Princeton and Harvard. JD Vance? OSU and Yale.

But you? Nah. Can't have the common folk bein' "overcredentialed". Might start gettin' uppity and askin' too many questions.

Best to leave all that higher learnin' to our new ruling class and be properly thankful for any table scraps they toss our way...

So the 'hyperloop' people have a cool website; while the 'train' people are just plain getting on with building stuff; whether conventional or the now-quarter-century-ish old maglev option.

Looks like someone signed up for another round of 'faff with apps vs. offshoring our entire high tech supply chain' and hoped it would work better this time.

And some dumbass 'managing director' is telling us that a gigantic safety-critical vacuum system is 'not effected by strikes'; more or less because he has no idea what the maintenance and operations would involve? Truly a joke telling itself.

It's easy to have unique keys in your spreadsheet so that you can easily relate information on different sheets to one another. The problem is, actually doing the processing that a SQL server would do trivially is irritating, and then it will be processed slowly every time. Whatever Excel does or doesn't cache, it isn't enough. You can do big complicated things, but they work slowly, and maintaining it is irritating at best. When you do complicated things either your formulas get long, or you wind up having to write code, or in fact often it's both. At that point you're way better off IMO doing it in something else so that at least performance is good when you're done, and you never have to screw with editing a long formula.

That's exactly why it should be in a database and not a spreadsheet. Spreadsheets are best when you have a reasonably limited number of columns. It's also a horrible PITA to use them as a relational database (it's more or less possible, but you don't want to do it) so hiding pieces of that complexity in other sheets in order to limit the data the user interfaces with on the main sheet is just a lot of extra work you wouldn't have to do if you used another solution.

It doesn't really matter where it fails, if Excel can do it and Sheets can't then Google has to admit inferiority to Microsoft which is never a good look.

Biden went around congress to fund a different genocide. Pretty words, but living up to them is another matter.

They do. Some people don't use them; and (if disciplined) use one or more worksheets to store data and refer to it purely internally and (otherwise) just sort of ad-hoc mix data and formulas.

In some cases a database connection is where the data comes from; but the number of cells grows because it's conceptually easier(and in practice often less opaque, given the ugliness of displaying very large cell contents) to munge on the data step by step rather than trying to ram everything into one transformation.

Coming from the IT side; and having to field questions from the perpetrators of some absolutely hideous excel sheets from time to time(no, I didn't even know that there was a way of creating a type of embedded image that actually quietly triggers the print spooler subsystem to do something that generates a new image based on the contents of another region of the spreadsheet, still don't know how they did that; but it's objectively depraved) I understand the hate; but I do have to admit that spreadsheets are pretty good for napkin-math thinking-it-through type processes.

Like when you work it out on paper; you've got your input, then you have a cell with the contents of the first transformation you wanted to make, then the second, then the third, and so on, and at each step you can think "does this value make sense?"

It rapidly gets out of hand in quantity; but as a rapid sketchpad for thinking something through you could do a whole lot worse. It's also tempting(again, tempting down the path of darkness in quantity) for dealing with jobs that need both a bit of string munging and a pretty-printed output.

You send the intern down to storage with a barcode scanner and have them start snagging SNs and MACs and stuff from the shipment of new gear. Turns out various vendors use different prefixes on different barcode values to inform their own ERP/inventory system/warehouse people which of the 5 closely spaced barcodes their scanner hit. And each vendor uses a different set of conventions, and while obvious enough they aren't documented. Ok, no problem; intern comes back with raw list; all the Lenovo SNs get a 'last x characters' substring; all the Cisco MACs get another transform, whatever.

Obviously if it were your inventory/warehouse system you wouldn't be treating the barcode scanner as a raw HID device and doing ad-hoc transformations, there would be a program that automatically uses the prefixes to populate the correct parts of the form; but you want to stick your head into ERP project hell rather than come up with maybe a dozen lightweight string manipulations? Obviously, you could also do it in your choice of scripting language and iterate through one CSV to create another; but that mostly just conceals what you did from anyone who doesn't use that scripting language; while you can walk basically anyone employable through the logic of the spreadsheet prettifying.

The problem is that the LLM only does one trick. When you start integrating other software with it, the other software's input has to be fed in the same way as your other tokens. As the last paragraph of TFS says, "every clock check consumes space in the model's context window" and that's because it's just more data being fed in. But the model doesn't actually ever know what time it is, even for a second; the current time is just mixed into the stew and cooked with everything else. It doesn't have a concept of the current time because it doesn't have a concept of anything.

You could have a traditional system interpreting the time, and checking the LLM's output to determine whether what it said made sense. But now that system has to be complicated enough to determine that, and since the LLM is capable of so much complexity of output it can never really be reliable either. You can check the LLM with another LLM, and that's better than not checking its output at all, but the output checking is subject to the same kinds of failures as the initial processing.

So yeah, we can do that, but it won't eliminate the [class of] problem.

Every tech company needs at least three things to start with: The business guy, the brain, and the lawyer. Ideally there should also be a marketing guy, but you can add them in later. Also, none of them have to be male, I just like saying "guy", buddy.

Yes and no, depending. If you are building an application in Excel, yes, all you said is true. If you are using one, no, none of it is. Spreadsheets can be set up such that the user just stuffs data into them where they are supposed to, then clicks a button to get results. Or maybe they don't even have to hit a button.

For the simplest useful example I can think of, I put together a spreadsheet which produces a table we use for asset valuation. This spreadsheet changes every year. If you load my spreadsheet, it will be correct for the current year. No user has to think about that at all, they just load it and get a correct table. You can extrapolate this to basically any level of complexity because Excel has VBA and you can script everything. The user just follows instructions, and they aren't even allowed to edit any cells which could break anything.

In case anyone is going this far down the hole, it turned out great. Even though the item was shipped from the US, because the seller didn't respond I got a refund without having to return it.

So far Aliexpress has been responsive to 100% of my issues and I only have needed to be a little patient and not expect everything to be solved immediately or arrive immediately.

I agree that a database-backed application is the right way to go for that much data. However, Finance used Excel because they could. We all like to talk about how bad an idea it is to do that, but Excel brought financial computations on large data sets to people who can't write any code. It has enabled thousands upon thousands of businesses to do things they couldn't do before without paying a programmer to develop a solution they cannot maintain. The fact that other spreadsheets regularly crater when handed data that Excel has no trouble with is exactly why we have so much Excel.

I like to use Drupal to rapidly create database applications which can handle a lot of data without writing code. But I wouldn't expect someone in accounting to be able to do that at all, and that just shifts the problem domain. Instead of getting stuck with Excel, now I'm getting stuck with Drupal. All of the logic just winds up in a different system that you can't trivially transfer it out of, so you have the same exact maintainability problem, except more people know how to work with Excel.

When Commerce Secretary Hoover got Congress to create the FCC's predecessor in 1927, it explicitly required spectrum allocation to be based on "the public interest", overturning the private property rights common law had been developing. This was done at the behest of the new radio network cronies. This led to all sorts of censorship, eventually enshrined as the fairness doctrine. The FCC also flexed its muscles to delay FM radio, cable TV, cell phones, color TV, WiFi, and I forget what else, by 10-20 or more years.

There's a great book on this, "Political Spectrum", by Thomas Hazlett. A good review: https://www.hoover.org/researc...