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

This is wild. Is it part of Python's specification, or an implementation detail of CPython?


As far as I understand, CPython implementation is THE specification. Some billions dollar ERP system firmly rely on this behavior, btw.


Yeah, I was afraid you would say that.


Just check with pypy and Graalpy. Both support this as well.


Is the question whether multiple base classes are part of Python’s spec, or if the ability to assign to `__class__` is part of the spec?


"Security by Obscurity" is being replaced by "Security by Velocity"?


The Military has the "Survivability Onion", Security through Obscurity is the "Don't be seen" layer, while "Security by Velocity" would be the "Don't be acquired" layer.


Same. My left pinky is so much happier on a Mac keyboard. Command + Shift + Tab on Mac is so much easier than Ctrl + Shift + Tab on Windows.


Oh goodness, I forgot that this was lodged somewhere in my brain


The idea is that you can solve 3SUM by solving an instance of Triangles in Sparse Graphs, but 3SUM produces instances where those graphs are lopsided (i.e., tripartite graphs where one of the parts is much smaller than the other two). They found an efficient algorithm for those kinds of instances, and therefore an efficient algorithm for 3SUM.


Oh wow, that is truly awesome then! I thought it was a qualifier, but it actually is the means of solution (yeah, confusing title).


Huh, good point. I wonder if this is the beginning of the end of constant phone upgrades. It used to be that new phones had much better hardware, so software that was only tested on new phones would make an older phone grind to a halt. But if the upgrades are much more incremental, perhaps a phone will last a lot longer?


The people who I knew that upgraded every 2 years stopped doing that nearly ten years ago now. Smartphones barely get better, why get a 49€/month contract when you can get one for 15€ instead and not have to migrate phones every two years upon contract renewal when the new phones aren't significantly better anyway?


We got an Advance Wars bot? Say more...


I only saw this vid https://www.youtube.com/watch?v=hdxAmJsspcA

clickbait title and the bot isn't at "top players struggle to beat it" level - but it's no longer a casual walk in the park like the default ai is, so the progress is massive


Seems to be "JuggerMaster_BOT" on AWBW.


Wow, this is incredibly cool. I can't believe this stuff hasn't been ported into Excel.


From this fact alone you can infer that 80-90% of people use excel as a glorified calculator.


Right, and that's why it doesn't really matter what innovative things don't get added to Excel because people wouldn't be using them.

Spreadsheets at their core are a visual intetaction model; a table with cells that can affect other cells. Beyond that core, you can do whatever you want - including with Excel, so the 10% that don't want to treated as a calculator can do so with a little bit of bespoke programming.

I've implemented several business applications where Excel was the user agent against specialized backend services. This was before the browser took over the front end in developer's mindset.


And a glorified database, and chart making tool, and whatever business app they can hack together.


Some people even make art in it! Incredibly flexible tool!


True


Right. And some hardware improvements will speed up both grep and Luna, which won't close the gap.


not necessarily, one may be easier to parallelize while the other suffers some serial computation bottleneck.


Grep is trivially parallelizable if you care to do it though.

https://iepathos.github.io/ripgrep/performance/#work-stealin...


Storage access isn’t, though. You have to read every byte of a (non-sorted) file to find words in it. And whether it’s disk or RAM, the bandwidth is usually a key constraint.

That’ll be just as true for an ASIC NN as it is for good ole grep.


When storage bandwidth is a big enough problem, that will get addressed.

NVMe v1 wasn't released until 2011 and there was no hardware available until 2012. Before that the fastest drive interface was 6 Gbps SAS. Then we got 4 GBps (32 Gbps) with NVMe v3, 8 Gbps (64 GBps) with v4, and 16 Gbps (128 Gbps) with v5. V6 is slated to double again. v7 is currently planned to double that. This is less than 15 years of progress.

In the 1990s, we went from 33 Mbps to 66, to 100, then 133 with IDE. We went from the 40 Mbps of 1986's SCSI 1 to 80 of SCSI 2 in 1994. Since then parallel SCSI has gone to 80, 160, 320, 640 (Ultra 2 wide), 1280 (Ultra 3), 2560 (Ultra-320), and 5120 (Ultra-640) Mbps.

SAS has also gotten faster, with 6 Gbps, 12 Gbps, and 22.5 Gbps. NVMe is still lower overhead and lower latency.

Memory bandwidth can also be addressed. Stock servers with EPYC are 16 channel DDR5. That's 409.6 GBps. Four channels of DDR3 was only 102.4 GBps. Video and accelerator card memory bandwidth is also increasing.


Bonus: if you write all your tricks in a document, people will love your document. Whenever I offer a new student my CHEATSHEET.md file, their eyes absolutely light up.


You have a link? :-) (Still a student)


Mine is unfortunately pretty specific to the HPC clusters we use. Maybe I should pick out the more general bits and make them public some day...


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

Search: