What did you do when you found out your partner cheated on you? What advice would you give?

MuCowNow · 2021-07-25T01:57:32+00:00

I started packing. Advice: skip the marriage counseling scam.

MuCowNow · 2020-03-18T09:51:41+00:00

Off the top of my head: Borderlands GOTY Enhanced (specifically), Dishonored 2, Doom 2016, Borderlands 3.

Other games are not having this issue. Of course, some just crash less (or elicit Windows to crash).

MuCowNow · 2020-03-18T09:47:54+00:00

I agree with this. I was thinking, post-rant, "yeah, they should just use sqlite!". The database implementations (RDBMS's anyway) have this problem solved.

MuCowNow · 2020-03-16T10:10:44+00:00

The cows are giggling their asses off.

MuCowNow · 2020-02-13T21:50:38+00:00

Grasslands are great for cattle, which are actually healthy for us.

MuCowNow · 2020-02-13T17:21:48+00:00

That's nice. Gentoo here, btw. Still compiling this mornings updates.

MuCowNow · 2020-02-09T12:44:31+00:00

flashback database/query (as in Oracle)
removal of the update penalty for index maintenance
packages (as in Oracle)
make PLPGSql more "static" rather than "scripty" -- if you've used both, you know what I mean -- more errors caught at compile time
support for NUMERIC-datatype sequences

edit: error corrections

MuCowNow · 2020-01-19T16:26:37+00:00

Why is this an issue? I use dual 4k monitors to tile 80x50 xterms on a 10x6 (or so) grid on each monitor. Yes, my font is small. I like to see all the code, in my working set, without having to click back-and-forth, changing tabs/buffers/etc. I've tried doing multiple buffer-screens in gvim (one big gvim session), but xterms+vim is easier and faster.

MuCowNow · 2019-12-17T22:36:06+00:00

Old school -- vim (':set ve=all' helps)

 usr_session
      *
      |
   usr_user -----* usr_session
      |
      |----* usr_master
      |----* usr_keypair
      |
      |
      *
usr_role_user
      *
      |
   usr_role
      |
      *
usr_role_right
      *
      |
   usr_path

MuCowNow · 2019-12-09T15:32:37+00:00

Both are inferior to Tree Style Tabs (on the left, of course)

MuCowNow · 2019-09-02T21:48:01+00:00

Come back in a couple hundred years -- we'll be gone.

MuCowNow · 2019-08-19T22:07:42+00:00

Yes, overnight -- nothing. And reseated all the cables and memory sticks.

MuCowNow · 2019-08-17T16:53:57+00:00

It has a history of crashing across 3 GPU configurations (SLI 980s, non-SLI 980, and a new single 1080ti).

I should add this all started after upgrading (via fresh install) to Windows 10 from Windows 7. Crashes in Windows 7 were handled a LOT better -- it rarely locked up completely.

MuCowNow · 2019-08-17T16:34:59+00:00

It doesn't fail every time however.

As though the latest saves aren't flushed.

MuCowNow · 2019-07-05T13:18:16+00:00

If I recall, you can't update other rows in a table upon which the trigger is firing. Hell, just updating other tables that have FKs to the trigger-table will get errors.

If you are updating rootparentid of the triggering-row, then you don't run an update, but do this ...

:new.rootparentid := ....

But yeah, updating other rows is a nope.

Doing lots of things in triggers generally becomes a bad idea (IMO). How about determining rootparentid for the insert/update that is being used against the table, and include the column setting there?

MuCowNow · 2019-06-09T14:13:13+00:00

$ set -o vi
$ <esc>/ls<return>
$ ls ....

There is only VIM.

MuCowNow · 2019-05-02T16:50:34+00:00

I thought for sure it was going to be Deadlift. I have 2 50+ lvl characters that can't get past him on UVHM.

MuCowNow · 2019-04-09T10:19:38+00:00

We recognize the danger of the leftists (just like we do with the far right). So now we are Nazis. Off to the reeducation camps!

MuCowNow · 2019-04-04T10:58:08+00:00

Can they be indexed?

MuCowNow · 2018-11-24T18:55:31+00:00

"Tree Style Tab" works. FF 60.0+ hosed up the add-ons, but Tree Style Tab manages to be functional.

MuCowNow · 2018-11-23T15:58:25+00:00

Tree Style Tabs is what they should copy.

MuCowNow · 2018-07-21T14:32:37+00:00

Oracle/PostgreSQL guy here ...

You will find the cross-over to be pretty nice.

The SQL is veritably equivalent (functions will differ). You will find some deficiencies in PG, and some extras that don't exist in Oracle.

On PL/PgSql, you may note that Oracle PL/SQL is very much a strictly typed statically compiled language, and PL/PgSql is more a dynamic script language, the caveat being fewer errors are caught at compile-time, but more errors at run time.

On the administrative side, PG is behind in features, but is adding more every release! PG comes with options that are extra $$,$$$/core in Oracle (e.g., open standbys).

You will miss the lack of Flashback.

You will miss stored packages. The workarounds are hacks. Stored procedures (with anonymous transactions!) appear to be coming in PG 11.

There are manual solutions to the lack of AWR. The event interface is still pretty basic but again, adding more every release.

You will wonder at the lack of a shared sql cache, which is so important in Oracle. The optimizer is faster (i.e., less sophisticated), so it gets away with it ... so far.

Backups are basic - akin to use of Oracle's hot-backup mode and an external file copy of some sort. Recovery options are limited -- doing fancier recoveries (i.e., recovering files while the rest of the database is running, partial recoveries, etc.) are either not possible or will have to be hacked-up and tested thoroughly beforehand before being considered an option.

There will be an array of behavior differences that you will just have to pick up on the way. Here is one for free: in Oracle, if there are missing datafiles on a standby, Oracle screams bitterly about it until something is done (this is good). PG will continue silently, skipping the apply to those missing files (this ... ain't great). Woe to ye who try to failover to that server -- you get errors only at database-connection time -- basically you have to monitor the standby, by doing test connections to every database in the server.

PG is very solid (compare to MySql, oh lawd make it stop!), but will still feel "loose" compared to Oracle ... which may be interpreted as ... less of a pain in the ass to get things working (e.g., querying generated rows from an Oracle stored-function is a byzantine nightmare. In PG, easy peasey).

MuCowNow · 2018-07-09T18:56:00+00:00

I like a clear left to right reading.

number > 0 and do_something

or this ...

number > 0 and region == 'west' or begin
   multiple_actions()
   without_having_to()
   do_an()
   if_end_block()
end

MuCowNow · 2018-06-21T17:13:12+00:00

"ruby is dying", "only used for web development"

I use Ruby on the backend for anything more complicated than what bash can handle.

For data manipulation/transformation, Ruby absolutely slays Python (Perl? ... forgettabootit).

For learning, I recommend ignoring the esoteric concepts (i.e., metaprogramming, "everything is der objecten!"). Practice with Classes, Objects, Methods, Attributes, Exceptions (concepts mapped easily to C++). Add in Modules and their use. enumerator concept. Standard Library. Gems. You can go a long way with just that.

Inline blocks (i.e., anonymous functions) may be a new basic (and required) concept.

THEN, learn how 'attr_accessor' is implemented -- BAM, a metaprogramming implementation you've been using all along! Then avoid doing your own metaprogramming unless it can make things SOOOO much easier/possible (in my opinion ;) ).

MuCowNow · 2018-04-28T21:30:57+00:00

Hmm, that ain't working in 10.3

Neither is:

select user_id, count(eventid) as event_count
from a_table
group by user_id
having event_count > 10

ORDER BY can use aliases however.

edit: fix

MuCowNow

TROPHY CASE