Hacker Newsnew | past | comments | ask | show | jobs | submit | john_miller's commentslogin


Marc Rich appears to have been comparable in severity of fraud but avoided conviction let alone all the other attention grabbing things Sam has done. Not to mention all the Israel connections.

If Sam has a pardon coming then he’s done as much as he possibly can to make it damaging to the pardoner. Can’t see it happening. Parents, maybe. They haven’t played this like asshats.


What's the battery life like on linux?


That's gonna depend on the distro and kernel, as different ones have different drivers, different power saving things, different apps. In general all modern distros should have decent support for power saving out of the box, but things like wifi cards typically have crap/buggy drivers when it comes to power saving (but again it depends on the hardware and driver)

That said, the spec sheet MobileMark benchmark says battery life is as good as 14.3 hrs in max battery setting on WUXGA Low Power (non-touch), Win 11, 52.5Wh battery, versus a performance mode getting 5.0 hrs on 2.8K OLED (non-touch), Win 11, 39.3 Wh battery. With 'local video playback' lasting longer. So I guess it's very hardware and use-case specific. (https://psref.lenovo.com/syspool/Sys/PDF/ThinkPad/ThinkPad_T...)


Eight or ten hours? I don't take a power cable with me for the day. Would probably be better if I worked out how to set any of the power saving things, this is Debian out of the box. That's mostly showing emacs, I expect it would be worse with a browser.


I'm on a Zen3+ APU (Thinkpad Z13) and TLP has worked great for me. TLP has nice out-of-the-box defaults so you don't need to tweak anything if you'd like, but you may need to disable any existing power management systems, if you're using a full-fledged DE, as they could conflict.

Two cool things that TLP does is allow you to set battery charge thresholds for better battery longevity (I limit mine to 80%), the other being automatically changing the energy performance preference (EPP) in the amd-pstate driver, so if you're on battery you could get it to automatically switch to power saving or balanced powersaving etc. I get an 8-10 hr battery life even with the 80% cap capacity, with several MS webapps running in Edge (Wayland), including Teams and Outlook, VS codium and Firefox running in the background.


We’ve got another visitor running Linux on it

https://news.ycombinator.com/item?id=38098486


No, the peak statement is not valid if inflation is considered. But the page has a "Adjusted for inflation" checkbox on the right, so you can see for yourself. :)


Do you have a link to the fed's minutes or to your thesis?


You can get the Fed minutes (iirc) back to the 80s on the main website. To get earlier ones (they go back all the way iirc), you can get them from ALFRED (there is tons of interesting data on there).


Teile und herrsche.

Divide and conquer.


fyi, paint is just an iframe containing https://jspaint.app/


very very ballpark:

2010: 2 billion internet users, firefox has 30% market share => 600mio absolute users.

2019: 4.1 billion internet users, firefox has 4% market share => 165mio absolute users.

That's of course very rough and may be a severly off, but the absolute number of firefox users seem to have shrunk.

https://en.wikipedia.org/wiki/Usage_share_of_web_browsers#/m...

https://www.statista.com/statistics/273018/number-of-interne...


> 4.1 billion internet users, firefox has 4% market share

Note that the denominator for market share as measured by StatCounter is "page views", not "browser users".

So for example, say you have 4.1 billion users, who use their laptop and phone evenly for their web browsing. On their phone, none of them use Firefox. All of them load the same number of pages every day. In this scenario, 4% of page views corresponds to 8% of users using Firefox on laptop.

Note that these are not realistic assumptions, of course: people vary widely in terms of how many pages they load, vary widely in terms of how their web activity is split between mobile and non-mobile, etc. For example, in 2010, I would bet that the average Firefox user used the web more than the average IE user, so the StatCounter number for Firefox was inflated compared to the actual fraction of users using Firefox.

If you want to measure actual number of Firefox users, you need to use a data service that tries to measure users instead of page views (i.e. not StatCounter).


> On their phone, none of them use Firefox

As the world goes mobile, that by itself is disquieting for Mozilla.


Yes, this has been a long-running problem, and was the impetus for Mozilla's attempt at FirefoxOS/boot-to-Gecko.

The current mobile situation is:

* iPhone: can't run Firefox there at all, really. There's Firefox for iOS based on WebKit like everything else on iOS, but I don't even know that StatCounter would count it as "Firefox".

* Android: Google for a long time had (and in many cases continues to have, as far as I know) agreements with OEMs that forbid a default browser other than Chrome. In some cases those agreements forbid preinstalling a non-Chrome browser at all, even as non-default. So you have to rely on people downloading an extra browser from the app store, and people don't do that much.

In addition to all that, "mobile" sites tended to be written to "WebKit", not "standards", for a while for various historical reasons. Unfortunately, at this point that's pretty deeply ingrained and people continue to do that, albeit with "Blink or WebKit" replacing "WebKit", which entrenches the problem.


I don't understand why they sunk so much money into Firefox OS when they could have much more easily released an Android spin that had Firefox by default, along with other privacy enhancements.


I think they missed a huge opportunity in about 2014/2015 to do what CyanogenMod was doing, as a clean/no-nonsense power user variant of Android. Ultimately the Cyanogen company leadership made poor choices and killed their relationship with the largest phone manufacturer that was shipping their OS on the phones (OnePlus), who decided to go and re-implement the same features in their own oxygenOS android build. Thereby killing Cyanogen as a company.


My understanding, and I could be totally wrong on this, is that at the time such an Android spin would not have been able to use things like Google's app store, and possibly things like Maps and whatnot, due to not having Google's browser as default.


Likely true. But there are options.

* it could come with an alternative app store

* maps can be used as a web app (how is that different from Firefox OS?)

But yes it would look more like Amazon's offering than Google's. Look where microg is now, though. That is without Mozilla's backing.


A bit tangential to your point but firefox for android isn't bad. I am using it to type this.

Not as snappy or polished as chrome on android to be honest.

I personally switched to it because I felt I give enough data to Google as it is. Probably not a great reason, because they still get a lot of data from me.


Sure, I use Firefox for Android as well. The "no one" was for ease of illustration; the general point is that Firefox market share on mobile is different from desktop and that this affects per-view share more than per-user share. Of course, to the extent that someone only uses a mobile device to access the web, per-user share is affected too.


Worrying and indeed not good for Firefox, if correct.

However, when you simply multiply "browser share" with "amount of 'internet' users, you may very well make some grave mistakes. E.g. does "Browsing Tinder" count as 'internet user'? Someone updating their instagram app? If so, you do miss a lot and maybe the numbers go very far in either direction when corrected?


Just incredible how mozilla killed firefox with so many short sighted actions including taking google's money.


but probably not to "Contributing Editor[s]" and the like


// call /MyPage?par1=hello&par2=42

const MyPage = (props: { query: { par1: string; par2: number } }) => ( <div>{`${props.query.par1}-${props.query.par2}`}</div> );


break != brake!


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

Search: