https://news.ycombinator.com/item?id=36776603
Glad this is getting more exposure.
In my opinion 2% is probably too high.
"There were 5.40 billion sessions over the past 90 days.".
2% is 108 million sessions in the last 90 days.
2,545 karma · joined September 26, 2014
https://news.ycombinator.com/item?id=36776603
Glad this is getting more exposure.
In my opinion 2% is probably too high.
"There were 5.40 billion sessions over the past 90 days.".
2% is 108 million sessions in the last 90 days.
Maybe I don’t need to query the file size at all?
with open('myfile') as f:
data = f.read()
I'm not much of a C programmer myself. but I at least reported part of the issue to Python: https://bugs.python.org/issue45944This is the fastest way to read a file on python that I've found, using only 3-4 syscalls (though os.fstat() doesn't work for some special files kernel files like those in /proc/ and /dev/):
def read_file(path: str, size=-1) -> bytes:
fd = os.open(path, os.O_RDONLY)
try:
if size == -1:
size = os.fstat(fd).st_size
return os.read(fd, size)
finally:
os.close(fd)Are there shortcomings with the built-in feature compared to your code?
https://developer.mozilla.org/en-US/docs/Web/API/HTMLElement...
https://developer.mozilla.org/en-US/docs/Web/API/HTMLElement...
https://developer.mozilla.org/en-US/docs/Web/HTML/Global_att...
Long term the plan is to 100% remove the GIL from python.
From the article:
> Long-term, we want no-GIL to be the default, and to remove any vestiges of the GIL (without unnecessarily breaking backward compatibility). We don’t want to wait too long with this, because having two common build modes may be a heavy burden on the community (as, for example, it can double test resources and debugging scenarios), but we can’t rush it either. We think it may take as much as five years to get to this stage.
Under base assumptions it also says:
> We want to be very careful with backward compatibility. We do not want another Python 3 situation, so any changes in third-party code needed to accommodate no-GIL builds should just work in with-GIL builds (although backward compatibility with older Python versions will still need to be addressed).
- No download bar to show actual downloads (downloaded files are hidden under a menu icon)
- No built-in page translate
- Search: is in bottom left rather than top-right which is pretty standard in most UIs.
- Search: would be nice if "Highlight All" were on by default (though it's caused me problems on Chrome with large documents so I can see off by default having some advantage.)
- Search: most of those options should probably be hidden under "advanced" or some expandable menu.
- I don't like the scrolling tab view where I can only see less than 10 tabs at once. I'd rather they get really tiny like on Chrome rather than totally hidden. Otherwise it's unclear to me at a glance how many tabs I have open.
- Youtube seems to have higher CPU usage compared to chrome (at least on MacOS x86, non-fullscreen)
- Tabs are too easy to mute and seem less intuitive which ones are playing.
- Dev tools doesn't have the “lighthouse” audit tool.
- Would be nice if cmd+shift+n shortcut matched webkit/blink behavior. I'm slowly learning to use cmd+shift+p instead, but being consistent with all the other browsers would be nice.
If it falls below 2% it may lose official support on .gov websites according to https://designsystem.digital.gov/documentation/developers/#b...
> In 2010, US attorney Sean Flammer ran an experiment. He asked 800 circuit court judges to side with either a traditional ‘legalese' argument, or one in what he called ‘plain English'. The judges overwhelmingly preferred the plain English version (66% to 34%), and that preference held no matter their age or background.
> Put yourself in your reader's shoes when you're writing; what are they going to be most interested in? We're often tempted to explain why we've done something before we tell people what the thing actually is — especially if it's bad news or an uncomfortable message. But if your first question is what does my reader really need to know, then you can't go wrong. Are they more interested in the process we took to decide something, or how that decision affects them? (Hint: it's almost always the latter.) That doesn't mean we shouldn't explain our reasons, it just means we should explain what the impact is first.
Here's the timeline the way I think about it:
- 2008-2012 Python 3 becoming usable (byte formatting, six library)
- 2012-2016 Libraries (Django, etc) becoming compatible
- 2016-today Applications (Trac, Ansible, Chrome, etc) becoming compatible.
It took a lot of time for the ecosystem to be ready. Yes, there was a lot of stubbornness, but that's reality.
There are many things that could have been done to make the transition go smoother.
Python has an Iterable type class for this.
https://docs.python.org/3/library/typing.html#nominal-vs-str...
https://docs.python.org/3/library/collections.abc.html#colle...
Sounds like html5lib has been asking for funding, but doesn't look like there's much progress. https://github.com/html5lib/html5lib-python/issues/361
$19.95 per month vs $20 per year.
I guess it’s time I drop IE11 support.
Also https://ping.pe/ is good.
They probably want to put pressure on publishers to use newer libraries that don’t need administrative permission, so hopefully eventually getting a version of the program that doesn’t need admin. Encouraging better security hygiene.
I agree that user-space compromise is still really really really bad.