Well guys, I have to say, you suck, we are further away from our one billion day goal than we were yesterday! But hey, I guess that means tomorrow is just another day to try. We have not seen any changes in the top ten so don't hold your breath. But nonetheless, let's dive in.
Shlouski keep himself in the number one spot today despite his power outage, taking the throne with 448,246,714 points, he did manage to outperform the next down the list but it was certainly close and he ca
Usually I try to limit my direct interference in the event, instead I usually like to ask open ended questions. But today I come to you all with a humble request. We are so close to see a billion point event day here that I just need to ask, can you push it some more, even if it's just for one day. Let's cross that billion point threshold together, united as a team.
For the firth day in a row we can see that Shlouski is sitting on that throne, he is really giving it one, despite thi
Usually on day three I announce that we have hit half a billion or one whole billion points. Well for this event I can proudly tell you all that we are just a little shy of two and one half billion points. It is in this that you can see just how far we have come as a team, and how far our technology has come.
And for the third day in a row we are seeing Shlouski sitting on the throne with 263,705,429 points, it is incredible to see just how far this lovely fellow brit can go pumping
So first thing first, Igor did not truly jump 130 ranks, there was a data issue on the last rankings, but this does not affect the integrity of the data, the issue was with the user entered data that was corrected yesterday after the posting of the ranks and blog post.
Sitting on the throne for a second day in a row we have Shlouski, with 167,910,201 points on the second day of the event it can be easily said that he is the man to catch. Producing slightly shy of 100 million points
Once again we get to enjoy the daily rankings of a folding month.
Ladles and Gentlespoons, here on the team many of us look forward to this event, year after year we come together as a team, to join together, to fold together, to compete together, but in the end the only true winner is science.
It is always a great pleasure for me to write the first blog post, the first of many to come over the next five weeks. It is always interesting to see who has already leap out of
So here we are, yet again another year has passed up by and we are once again cranking the dials to 11.
I know for many of you this year will be painful, we are seeing a global energy crisis of the likes many of us have never seen before.
Some of you, this will be the first time in which you have joined us, and for a very select few this will be your chance to get the event veteran badge.
For those few of you out there who join me in the elite club of joining every single
Well here we are, once again we have found ourselves staring into the abyss, trying our best to scrounge up hardware from down the sofa cushions to put to work!
I would not have even remotely imagined that five years ago we would be here, a top 3 team with regular events, seeing prize pools like we have for this event but here we are. It is incredible to see you guys come back year after year, to push forward the team, to come together and compete.
I'm not going to lie
There's an Olde English saying out there that goes something like this: He who buyeth a laptop just because it looketh cool shall risk developing cancer. OK, maybe I made that up. Still, I feel like this is one of the most interesting design flaws to ever come out of the tech industry, and one that deserves to be far better known because of just how pathetic it is.
When Dell launched the original XPS 12 in 2012, it was marketed as a "MacBook Air and iPad melded into one device," despite
Not to take a piss on python , i actually like the languagee , especially the development speed you get with it.
but...
only in python are things that are an order of magnitude faster in other languages actually much much slower:
Branching logic vs Branchless Logic:
import random
from time import perf_counter_ns,sleep
testnrs = [random.randrange(0,5,1) for _ in range(2**20)]
def branch(nr,idx,result):
if nr < 1 :
result|=int((str(abs(result))*9)[1:3])
elif nr ==
If you didn't see my last post on here, WordPad wasn't starting as quickly as it should've been on my laptop. I tried everything I could possibly think of to fix it or at least diagnose it, but everything failed.
I was recently thinking about things that could have some form of input into how WordPad works (which isn't much, it's got about as many settings as a light switch) and thought about the Windows Print Spooler service. For those of you wondering what the hell I'm talking about, t
Whenever I write one of these posts, there's a good chance that I'm doing so using WordPad. I know some people are probably wondering why, so I should probably start by answering that.
I don't use Microsoft Office because I'm not paying $80 for a word processor. I don't use LibreOffice because it's crashy, needs to be updated manually, and unfamiliar. I know WordPad has no spell-checking, but that doesn't bother me because I'm confidrnt enough in my spellig. I know WordPad doesn't ha
a 16 cylinder engine
a 4600 lb tow capacity
stiff suspension
an 5 star frontal collision rating
4 turbos
2 trims
Weird suspension trim (WST)
stiff suspension trim (SST)
an 4 star rollover rating for weird suspension
pros and cons
WST
pros:
less possibilities of a rollover
smoother ride
Cons: suspension bottoms out while accelerating (w/ trailer)
hitch does not attach some times
SST
pros: suspension will not
As the proud user of a tried-and-tired iPhone XS with an ailing battery and more scuffs than a drunk driver’s car, it should be fairly obvious that I’m not the kind of person who excitedly buys the latest iPhone when it comes out. Still, I often argue with the keyboard comedians out there who always make the same jokes about how a new iPhone is the same as the last one.
I’ve always disagreed with these people for several reasons over the years:
The camera usually gets a s
this was my first car made in 4.27 and my first car with a interior
containing 50+ fixtures and 3+hours of work
several keyboards
speed reduction
15x 16 cylinder engine prototype
traction control removed
so after postponing for 15years i finally decided to give vim a go....
these are my issues with it most of them are applicable to the out of the box fesh installation of it.
lets start with the first couple:
for a keyboard oriented editor (everything availeble from commands and functions without your hands needing to change positions ~ everything availeble from homerow) , to the point wer navigating a document (usually arrows) is duplicated to the keys hjkl , you do have
About a year ago, I received a Chromebook from my mom’s friend. Its end of support date was sometime in June of this year (2022 if you’re reading this in 2023, 2024, or maybe this blog will be like religious books and people in the year 4843 will have this read to them by their robotic dog who is also their dental hygienist), so she figured I might want to do something with it.
I genuinely don’t think I’d ever wanted a laptop less than that, because I’m sure we all know the hardware
here is another thing that really sucks hairy monkeyballs in any arch based distro:
so apparently pacman knows these two packages are actually the same as they occupy the same slot (conflict):
:: ki18n and ki18n-git are in conflict. Remove ki18n-git? [y/N] (=>both answers haave the same effect the process exits)
but even if sees the conflict it doent actually know these are the same packages,
since the -git version is installed lets check what version of the package is curren
sometimes the "everything is a file" approach on *nix systems is great sometimes its not really
especially when programming its not.
the filesystem structure of certain " special/magic" directories and there files is maybe unlikely to change in the near future. but
filepaths tend to be just strings most of the time. even when they arent at first glance if you follow the trail down to where they are actually constructed they usually end up being just a collection of hardcoded str
This was a lovely little sprint we had, an amazing turn out when you take into account the current cost of living crisis and to say we produced over 2.7 billion points and that something we all be proud of. No matter if you were a whale or a sardine, you were a part of this achieve and for that, you should be patting yourself on the back. Thank you to everyone who helps to make the events run smoothly and thank you to everyone who signs up for your understanding of my struggles.
Thi
I wrote this shortly after acquiring my new monitor in June of 2022 but seem to have forgotten to post it. Here we go...
A few months ago I wrote about how desperate I was to upgrade from my 17” Acer AL1706, as it simply wasn’t the kind of monitor I could see myself using into the foreseeable future. Sure, it was better than, say, a 2000s laptop screen, but calling a display better than one on a 2000s laptop is no different than saying your house is safer from flooding than a town in
Baha continues his push in the final days of the event, and if he keeps it up we will see him pushing up to 5th place by the closing whistle. Shlouski is looking so impressive, you can not help but appreciate the way they have smashed it and pushed the team to higher levels.
In first place, as has been the truth for the entirety of the event we have shoulski, with 394.2 million points, there is no way we won't be celebrating the legend by the end of the event at this point. miker07
It's looking pretty calm in the ranks today, cbogfoot is back in the top ten and Baha is looking poised to advance further up the ranks in the last couple days we have left of the event.
I'm not going to write out the ranks today, not much has changed and unfortunately I gotta get ready to stream as I'm running late, I hope you can all understand. Please find the ranks below.
Day Five Stats
Please remember that this is a friendly event, but we are all
