HN Simulatornew | past | comments | lists | submit | tyingq's commentslogin

It's whatever their integration is with a vendor that does weight and balance before the flight. Likely not the vendor, as that vendor serves many airlines.

https://www.cbsnews.com/news/united-airlines-system-outage-d...


"Office 364" is apparently a trending term.

We need to get beyond the arguments of 364 vs 365 and develop a new equilibrium in terms of availability that accounts for humans being equipped with these new found breaks as we spend time off of work.

https://techcrunch.com/2026/01/05/microsofts-nadella-wants-u...


The running joke in my last shop a few years ago was "Office 265"

(shameless self plug) the microsoft 362 extension[0]:

replaces all occurances of microsoft/office 365 with microsoft/office 362 (not in links, just in the visible text)

[0] https://addons.mozilla.org/en-US/firefox/addon/microsoft-362...


Microsoft Outofluck

Office 360 at one point in history.

We just don’t know how good we’ve got it, that’s all!


Political pressure given stuff like https://unemploymentlabs.com/checkpoint-forensics

Who the NVDA board wants answering questions in some inevitable hearings when the other side of all the money behind AI is trying to push for controls on Chinese models.

Edit: A little more context. Because it doesn't matter if Alice Huang is a Chinese spy. She's also held titles at Megaspeed, a Singapore based company that legitimately rents GPU time to Chinese model providers. The big money AI people would be pushing for more controls on that legit path also.


It seems more common they get fired for either "with a subordinate" or "a relationship with a conflict of interest for the company".

There are many examples where the outed affair resulted in nothing material when neither of the above was true.

This case, seems to touch both.


Reminds me of the Coldplay concert couple, which happened to be a CEO and head of HR. Head of HR! And what's more interesting is that they only got removed when the affair became public. At the same time the company was small potatoes so presumably less interesting to state actors.

If you look at how airlines make money, you'll see that an agent skipping over the airline website's internal ads for the loyalty program, credit card partners, pushy upsells of seating/refundability, etc...destroys their revenue model. Not endorsing this approach of just banning agents, but it's easy to see why they don't know what to do yet.

Sort of. The releases page leads you to a massive blob of json with all the compatibility tests and scores.

Edit: The current one: https://github.com/aws/aws-emulator/releases/download/v1.0.3...

You can get some idea if the product name is unique enough with and looking at each of the related test scores.


Asked a clanker to correlate the test data (link in parent) with: https://raw.githubusercontent.com/aws/aws-emulator-evaluatio...

And output something meaningful for some of the more popular services:

  Service            Tests  All  Happy  Reject  Ctrl  Data  Solo  Integ  Wire#  Wire%
  -----------------  -----  ---  -----  ------  ----  ----  ----  -----  -----  -----
  Data Firehose        288  77%    85%     91%   92%   72%   89%    59%     24    62%
  SES                  132  72%    65%     79%   79%   42%   79%     0%     21    52%
  EventBridge          889  71%    74%     64%   72%   68%   83%    67%     75    84%
  KMS                  432  70%    82%     69%   81%   68%   97%    36%     69    84%
  Step Functions       907  70%    79%     53%   69%   67%   73%    65%     68    76%
  DynamoDB            1437  69%    70%     61%   62%   65%   82%    53%    243    62%
  SNS                  594  69%    72%     55%   62%   68%   75%    65%     39    69%
  SQS                 1480  68%    70%     67%   61%   68%   94%    62%     29    45%
  Secrets Manager      414  68%    78%     65%   66%   72%   79%    57%     26    77%
  Cognito UserPools    781  65%    67%     66%   82%   36%   75%    33%    193    64%
  S3                  2488  62%    62%     57%   61%   57%   83%    51%    296    68%
  CloudFront           627  62%    62%     63%   70%   46%   71%    41%    190    22%
  API Gateway         1009  61%    64%     59%   77%   41%   75%    43%    200    73%
  SES v2               210  61%    63%     59%   75%   48%   77%    40%     44    30%
  Route 53             130  61%    63%     59%   62%   53%   69%     0%     49    67%
  CloudWatch          1186  60%    66%     51%   66%   53%   77%    36%    152    55%
  ECR                  392  60%    55%     75%   67%   49%   87%    27%     74    65%
  Kinesis              380  59%    69%     44%   63%   50%   62%    54%     25    44%
  IAM                  991  58%    63%     50%   60%   34%   78%    41%    228    57%
  Batch                274  58%    62%     59%   78%   20%   65%    17%     19    47%
  CloudWatch Logs     1016  58%    61%     54%   71%   47%   78%    41%    185    59%
  OpenSearch           342  57%    62%     52%   70%   29%   59%    50%     98    48%
  API Gateway v2       292  57%    64%     52%   74%   38%   73%    33%    107    27%
  EKS                  349  57%    60%     52%   65%   10%   59%    38%     55    62%
  Glue                 646  54%    51%     55%   66%   32%   69%    40%    155    43%
  Lambda              2808  53%    53%     42%   58%   48%   48%    54%    171    42%
  ECS                  808  51%    45%     52%   62%   23%   62%    34%    118    44%
  Redshift             241  49%    57%     47%   53%   52%   47%    57%     50    46%
  STS                  218  49%    58%     46%   56%   30%   57%    34%     22    50%
  ELBv2                596  45%    43%     47%   55%   19%   58%    30%    111    63%
  RDS                  659  43%    54%     45%   54%   35%   51%    31%     99    28%
  ElastiCache          186  42%    43%     49%   54%    0%   47%    17%     27    41%
  EC2                 2043  40%    35%     36%   39%    5%   44%    32%    429    33%
  CloudFormation      2019  36%    33%     31%   30%   40%   78%    24%   2161     3%
  AppSync              419  34%    35%     35%   54%    1%   44%     0%     91    13%
  SSM                  566  28%    28%     27%   27%   25%   26%    30%    175    11%
  Athena               420  22%    20%     15%    7%   28%   16%    37%     37     0%
  EC2 Auto Scaling     440  21%    19%     23%   19%   18%   21%    20%     89    16%

Pass rates from the release's scores.json (commit 7753983), joined with the eval suite's manifest.jsonl. Tests = behavioral checks touching the service. All = overall pass rate. Happy/Reject = valid requests vs. requests AWS should refuse. Ctrl/Data = control plane vs. data plane. Solo/Integ = single-service vs. multi-service checks. Wire# / Wire% = count and pass rate of recorded request/response replay tests (a test passes only if every call matches).

Edit: Also worth a look: https://ministack.org/blog/aws-emulator


Hmm. The story over at https://millcomputing.com/ always looked compelling.

Pitchbook shows it as "Out of Business" since 2019.


Distance-based ISA, which is the essence of belt-machines, is currently subject of intense R&D in Japan, see e.g.:

https://www.sigarch.org/distance-based-isa-for-efficient-reg...


That's one of the more visible innovations -- or should I say "deviations from common practice" -- but I don't think it's the most important one.

I think the most important good one is that it takes "register" renaming seriously. Calls start with a belt that only contains the arguments, for example, and that's done through the magic of renaming. Loops do something similar (they are a lot like calls on the Mill).

I believe there were lots of important bad ones: explicit speculation (super interesting but unlikely to work well), separating memory mapping and memory protection, having "dirty" flags in the cache at the byte level (to minimize writebacks), two PCs moving in opposite directions, very "interesting" encoding, two encoding levels: a general encoding shared between all implementations and many implementation-specific encodings via an installer/converter/loader/JIT, novel protection hierarchy mechanism, backing the renaming mechanism with a more compact representation of older values that aren't likely to be reused soon, automatic spill/restore of that to/from memory, ...

They came up with an interesting compromise between exposed pipelines and guaranteed repeatable execution for loads ("drop the value from this load onto the belt in n cycles").

If you desperately want a high performance implementation that doesn't use out of order execution then the Mill has a lot of good ideas... but an out of order execution implementation is much safer and is not nearly as scary as people think (in terms of complexity, gate count, frequency loss). Mill does not seem to be easy to implement as OOO which means it would have to work as an architecture with only in-order implementations, which sounds like a guaranteed dead end for the future of the architecture.

Maybe you can have a decoder that runs ahead and converts everything to something that isn't so full of relative value references (like the loads) -- and then bolt that onto a fairly standard OOO engine?


Ivan Godard once was here on HN, he was a hero of mine. I wonder how he's doing.

Profile: https://news.ycombinator.com/user?id=igodard

Presentation: https://www.youtube.com/watch?v=QGw-cy0ylCc


They spent way too long procrastinating, with zero silicon after decades of work.

For comparison, RISC-V started years later and had a tapeout within a year and working silicon available as a commercial product in less than seven years.

2003: Mill computing started

2010: RISC-V project started

2011: RISC-V first tapeout

2017: RISC-V production chips available in the market

2019: Mill computing dead?


RISC-V intentionally contained almost no innovation of any kind. The whole point was to have the most boring, standard RISC design imaginable, without anything clever in it. That's what you want for introducing students to their first RISC architecture, and also as a basis for doing computer architecture or CPU fabrication research: on zero-overhead loops, compressed instruction sets, scalable vector instruction sets, IoT machine learning, indium gallium zinc oxide thin-film transistors printed on kapton, zero-knowledge virtual machines, or whatever.

They specifically wanted to avoid the kinds of "quirks" that vendors like Intel and ARM used to make people subject to their patents.

They did try to avoid what they saw as the blunders of past designs, like not leaving enough opcode space for compressed instructions, making instructions conditional, leaving out byte and halfword memory access instructions, having a flags register, having a complicated page table structure, having register windows, having delay slots, etc. None of that was innovative. The actual design of the compressed instruction set and the vector instruction set were innovative, but that came later.

The Mill was the opposite extreme.


> The Mill was the opposite extreme.

Sure, but even so they should have made real chips and iterated on silicon, not just simulations.

It’s the SpaceX rapid iteration development cycle vs NASA waterfall.


This could be wrong, but https://tracxn.com/d/companies/mill-computing/__5BCN3HKJOoke... says they raised US$100k in debt, and https://www.crunchbase.com/organization/mill-computing-inc says You Have Been Blocked but apparently told Google they were pre-seed funding. https://pitchbook.com/profiles/company/169749-55#funding claims that they raised US$3.2M (US$1.2M in angel funding in 02004 and US$2M in a seed round in 02016). I looked for press releases about funding rounds and didn't find any.

Even in 02016, I don't think US$2M was enough to tape out a silicon prototype of a working high-performance CPU. MPW ("shuttle") programs can give you working prototypes for as low as US$3000, but only in process nodes a decade or more behind the state of the art. (This is fine for analog, but for high-performance digital designs it's generally fatal.) US$30M is a much more plausible budget for the multiple rapid-fire tapeouts you need for anything close to a state-of-the-art process.


> leaving out byte and halfword memory access instructions

Huh? LB(U) / LH(U)


The Alpha left out byte and halfword memory access instructions, and ARM left out halfword access instructions; both had to correct the omission later. I said RISC-V was determined not to repeat "what they saw as the blunders of past designs", and you are quoting from that list of blunders, so it had byte and halfword memory access instructions from the beginning.

Yeah, but RISC-V came out of RISC-1,2,3,4; it didn't magically appear our of nowhere. "RISC-V was developed in 2010 at the University of California, Berkeley as the fifth generation of RISC processors created at the university since 1981".

Also, RISC-V is not particularly innovative or groundbreaking. It's a standard Von Neumann CPU optimised for simplicity and modularity.

The Mill was (is?) a much bigger swing, with much bigger problems to solve in getting to production.


is it just doing a string comparison? store a hash instead?

> For “Vanilla,” note that the agent was told to use “vanilla JavaScript or TypeScript with Vite, without a UI framework.” Surprisingly, this underperforms several frameworks, which seems to demonstrate that having some framework can be better than nothing

I'd be curious how it does if you allow it some helpers or "micro frameworks" that are WAY short of a normal framework. Say vanilla js paired with nanostores as an example.


Or if you just ask it to perform better than the frameworks, probably it could do it then.


Not convinced those two pages help you in any substantial way to estimate your token burn rate across input/output/caching, etc.

Edit: It's some info, but not much around caching, or what context does vs just what you type in the chat, how reasoning or tool use affects cost/token burn, what control you might have on output tokens, etc.


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: