• 2 Posts
  • 242 Comments
Joined 2 years ago
cake
Cake day: July 4th, 2023

help-circle

  • A lot of them are dependencies of other plugins.

    Stuff like icons support, and every little feature. Neovim is extremely minimalist to start, so you need plugins just to get something as simple as a scrollbar lol

    Things like git status of files and file lines, all your LSPs, syntax highlighting (for each language you work with), file explorer, you name it, there’s a lot.

    But what’s nice about nvim is for any of these given features, there’s numerous options to pick from. Theres probably a dozen options to choose from for what kind of scrollbar you want in your editor, as an example.

    So you end up with a huge amount of plugins in the end, for all your custom stuff you have configured.

    You have to setup yourself (though theres a lot of very solid copy pasteable recipes for each feature):

    • Scrollbar
    • Tabs(if you want em)
    • bookmarking
    • every LSP
    • treesitter
    • navigation (possibly multiple of them, I use both a file tree, telescope, and harpoon)
    • file history stuff
    • git integrations, including integrating it with the numerous other plugins you use (many of them can integrate with git for stuff like status icons)
    • Code commenting/uncommenting
    • Code comment tags (IE TODO/BUG/HACK/etc)
    • your package manager is also a package (I like lazy for wicked fast open speeds, neovim opens in under 1s for me)
    • hotkey management (I like to use which-key)
    • prose plugins (lots of great options here too, I use nvim for more than just coding!)
    • neorg, so I can use nvim for taking notes, scheduling stuff, etc too
    • debugger via nvim-dap
    • debugger UI via nvim-dap-ui
    • lualine, which is a popular statusline plugin people like to have at the bottom of their IDE for general file info
    • new-file-template which lets me create templates for new files by extension (IE when I make a .cs file and start editting it, I can pick from numerous templates I’ve made to start from, same for .ts, .lua, etc etc)
    • git conflict, which can detect and work with detected git merge conflict sections in any type of file and give me hotkeys to do stuff like pick A / B / Both / Neither, that sorta stuff

    The list goes on and on haha




  • I think it can be long term a suboptimal strategy.

    A good relationship can take many years to grow, and it’s very likely that your best partner later in life is one who was there with you during the grind, who knows what it was like before vs after, and has the perspective.

    Ideally, who also worked hard on their own career at the same time.

    It’s nice to have someone to support you during that period of your life, who remembers the tough times and you can reminisce later once things are better.

    My partner and I have been together for 15 years now, and we both very much nostalgia all the time over when life was tougher, but also simpler.

    I think if you get a partner later when all the dust us settled, you’ll never quite be able to capture that same type if relationship and you’ll never get quite as close as you could’ve, cuz they simply just weren’t present for that period of your life.


  • The entire point of the format is to actively make it so you are no longer pressured to proxy cuz you need thousands of dollars in cards to function at the table.

    This is with the intent to make players want to actually go to their lgs and buy actual real cards, instead of ordering proxies from random companies in China.

    Trying to pretend that players feeling compelled to proxy their deck isn’t inherently unhealthy for the local game ecosystem is silly.

    The #1 thing LGSs want is bodies in the door. So if players are getting back into stores to buy a bunch of 50 cent cards, they probably are also supporting the LGS in other ways inherently.

    The current casual meta of 5 people sitting down and all of them pulling out proxied decks directly means 5 less instances of people actively walking into their LGS to shop.

    You can say what you want but as someone friends with LGS owners, I can definitely say the chilling effect of proxying on the casual economy has been very noticeable. The market for casual cards has heavily dried up.

    Tonnes of people take the next step of “well if I am proxying 10 cards why not proxy all 100 who cares”

    Shops demand for cheap staples dries up.

    Shops stop buying cheap staples bulk cuz they arent selling.

    Non proxy’ing players can’t find their cards that need… so they guve up and turn to proxying too

    You can see how that feedback loop is unhealthy, right? Thus here I am, promoting a format that aims to counter this feedback loop and try and inject health back into the local casual tabletop ecosystem

    So yeah, if you proxy in the aforementioned format, you are not playing in the “spirit” of it.


  • Commander is by far the most popular format for many good reasons.

    I however am not a fan of some recent sets design wise. Bloomburrow was peak though, and felt like a return to a more classic mtg experience.

    Personally I’m a fan of budget commander, where it’s still commander with these 3 deck building rules:

    1. Your total deck price l, if you price it online, cannot exceed $70 USD

    2. You cannot play any cards that have ever been banned in any mainstream constructive format (discluding rarity based formats like pauper)

    3. Proxies are not allowed, as it goes against the spirit of this format

    The core spirit is “stop feeling compelled to proxy shit, support your LGS!”











  • Okay but if that happens, musk is right that that’s a bit of a denormalization issue that mayne needs resolving.

    SSNs should be stored as strings without any hyphen or additional markup, nothing else.

    • Storing as a number can cause issues if you ever wanna support trailing zeros
    • any “styling” like hyphens should be handled by a consuming front end system, you want only the important data in the DB to maximize query times

    It’s more likely though it’s just a composite key…




  • They probably do use lots of NoSQL DBs too, which perform better for non relational “data lake” style architectures where you just wanna dump mountains of data as fast as possible into storage, to be perused later.

    When you have cases where you have very very high volume of data in, but very low need to query it (but some potential need, just very low), nosql DBs excel

    Stuff like census data where you just gotta legally store it for historical reasons, and very rarely some person will wanna query it for a study or something.

    Keep in mind when I talk about low need to query, the opposite high need us on the scale of like, "this db gets queried multiple times per minute’

    Stuff like… logins to a website, data that gets queried many times per minute or even second, then sometimes nosql DBs fall off.

    Depends what is queried.

    Super basic “lookup by ID” Stuff that operates as just a big ole KeyValuePair mapping ID -> Value? And thats all you gotta query?

    NoSql is still the right tool for the job.

    The moment any kind of JOIN enters the discussion though, chances are you actually wanna use sql now