minkeymaniac

I assume they mean.. have the test and then act upon it with diet/exercise/medicine to prevent the heart attack If you never had the test, maybe you don't know you are at risk and don't make any changes and then you get the heart attack

How long before we see this here --> https://killedbygoogle.com/

who can forget this scene... https://youtu.be/zJs9p-VNORw?si=sLF7ve6AhrQw8fNn&t=245

I remember using usenet newsgroups (outlook express anyone :-) The Wrox books had a mailing list where you could reply or ask questions by email... I used those a lot.. in the beginning to ask and in the end I was answering more and more

B (with the bird) brings back 100 guilder vibes. https://europost.nl/winkel/bankbiljetten/nederland-ba/nederl...

I just downloaded llama. ran this llama-cli -hf ggml-org/gemma-3-1b-it-GGUF

I am getting [ Prompt: 91.3 t/s | Generation: 171.8 t/s ]

This is on a GPU (RTX 4060)

Is this decent?

Same is true for Croatia.. food from Slavonia (near Zagreb) is very different from the coastal regions (Istria and Dalmatia)

Windows 2000 Professional was the non server edition no? That's the one I was running AFAIK.

https://en.wikipedia.org/wiki/Windows_2000#Editions

But you might be right by meaning consumer is non business user.. I also ran ME for about 2 weeks lol

And crazy themes I had the matrix one with the "dodge this" sound instead of a ping... good times

The different kernel for 95/98 was NT 4... Windows 2000 was unified, same UI for Consumer and Server

Normalize till it hurts, then denormalize till it works!

7 was a rewrite, from c to c++, also went from 2k pages to 8k pages

2000 for sure had instead of triggers.. I used them :-)

It went down 89% Between 1929 And 1932, it took 25 years to close above 400 again. https://denisgobo.blogspot.com/2008/12/how-long-did-it-take-... Of course with Dollar-Cost Averaging you will be buying at the low until as well

The step count in NYC stands out like One World Trade Center compared to the rest of the building when looking at the skyline ;-)

I listed some hard drives on Friday on eBay.. most of them refurbished... within 5 minutes got a message from a person who wanted them all... shipped them an hour later

I can confirm.. open up linkedIn.. hit F12 and watch the error count keep going up and up and up

Screenshots found here https://x.com/DenisGobo/status/2018334684879438150

Article is from July 2025, Gold was 3362 at that time

Yep, it doubled in the last 4 months https://www.youtube.com/watch?v=o5Zc-FsUDCM I upgraded my PC by adding 64GB.. two Fridays ago I sold the 32 GB I took out for the same amount of what I paid for the 64 GB in July... insane

Doubled in the last 4 months https://www.youtube.com/watch?v=o5Zc-FsUDCM

Upgraded by adding 64GB.. last Friday I sold the 32 GB I took out for what I paid for the 64 GB in July... insane

I never imagined that they could survive in Alaska. From the show Life below zero... take a look at these.....https://www.youtube.com/watch?v=YXq92PItsA0

Yes.. try moving that 36 inch Sony Trinitron from the car inside the house.. weighs 200 pounds+ IIRC....you need at least 2 strong people

unless you have more than 1 passport

in sql server, you can simply add a not null check constraint with nocheck (see my comment with full code)

ALTER TABLE foo WITH NOCHECK ADD CONSTRAINT CheckNotnull CHECK (id IS NOT NULL)

any new values coming in cannot be null but the values already in the table with null are fine... then you can update them to not null over time

If you don't care for old data having null , you could add a check contraint with nocheck (this is sql server fwiw)

for example

create table foo(id int) insert foo values (1), (2), (3)

insert foo values (null)

select * from foo

id

1

2

3

NULL

ALTER TABLE foo with nocheck ADD CONSTRAINT CheckNotnull check (id IS NOT NULL)

insert foo values (null)

Msg 547, Level 16, State 0, Line 13 The INSERT statement conflicted with the CHECK constraint "CheckNotnull". The conflict occurred in database tempdb", table "dbo.foo", column 'id'. The statement has been terminated.

However be aware that if you update an existing value to NULL, you will still get the error

update foo set id = null where id = 2

Msg 547, Level 16, State 0, Line 20 The UPDATE statement conflicted with the CHECK constraint "CheckNotnull". The conflict occurred in database "tempdb", table "dbo.foo", column 'id'.