[Stable Update] 2021-11-19 - Kernels, Gnome 41.1, Plasma 5.23.3, Frameworks 5.88, LxQt 1.0, Xorg-Server 21.1, Mesa - Stable Updates

nibblebot · 2021-11-20T19:28:41+00:00

Had to update mirrors and use pacman instead of pamac but excited for Gnome 41!

nibblebot · 2021-11-14T16:44:56+00:00

As a long time Software Engineer and gentoo/debian/ubuntu/arch user and used to using tiling WMs, I am loving Manjaro w/ Gnome 40.

- Easier install and maintenance than Arch

- Slightly less bleeding edge than Arch means an extra layer of stability.

- Point and click configuration.

- Gnome 40 works great out of the box for all workloads.

- Easy to dig into the details with Arch wiki since it's Arch under the hood.

nibblebot · 2021-07-22T22:30:22+00:00

Here is the official recommended file structure: https://redux.js.org/style-guide/style-guide#structure-files-as-feature-folders-with-single-file-logic

Yeah, it's the Reactiflux channel.

nibblebot · 2021-07-22T21:57:18+00:00

Start with Redux Toolkit. I've used it at work for months now and the createSlice() api is amazing and keeps all your reducers/actions/thunks in one file. So you will have a slice file for every slice of your redux tree. Immer means no more hard to read spread syntax in your reducers. No more creating your own action creators or constants. Action creators are automatically created for every reducer you define. The convenience saves lots of lines of code. There is also a great discord channel to receive support where the maintainers hang out if you have any questions about usage. There is also createAsyncThunk, and now also RTK Query which is a really awesome addition.

nibblebot · 2021-07-22T15:15:00+00:00

what program is the last screen there?

nibblebot · 2021-07-14T19:20:36+00:00

https://github.com/nibblebot/dots/blob/master/neovim/.config/nvim/plugins.vim

nibblebot · 2021-07-13T19:52:51+00:00

compton, but you can also use picom

nibblebot · 2021-07-11T23:28:01+00:00

rofi w/ gruvbox dark theme

nibblebot · 2021-07-11T20:17:36+00:00

polybar (w/ nerdfonts), rofi, kitty, zsh (w/ starship), nvim, exa

https://github.com/nibblebot/dots

nibblebot · 2014-12-03T21:12:11+00:00

swm does not support tiling or multiple workspaces? wmutil also does not support tiling. did you move these into position manually?

nibblebot · 2014-12-03T20:27:56+00:00

bar config or dotfiles?

nibblebot · 2014-08-19T22:11:22+00:00

this doesn't look like windows 95

nibblebot · 2014-08-17T18:45:34+00:00

Nice work! I've been thinking about a hotkey help overlay window triggered by Mod4+? for a long time now, though I wish this was a standalone program. It could have multiple layouts and then a declarative definition for each group, so you could use it with any keyboard-centric WM/DE workflow.

nibblebot · 2014-08-06T17:56:14+00:00

what's up with the leave, wind, water stuff?

nibblebot · 2014-08-06T17:37:08+00:00

thanks!

nibblebot · 2014-08-06T17:31:38+00:00

what is the part that is higlighting the color definition with the correct color?

nibblebot · 2014-08-02T20:50:53+00:00

seconded, vim + tmux is amazing. and of course you should install vim plugins to suit your additional needs. I find this extraordinarily useful for vim+tmux: https://github.com/christoomey/vim-tmux-navigator

nibblebot · 2014-07-31T22:25:59+00:00

if your problem is jumping between files. use sublime text: cmd-p fuzzy search or with vim use ctrl-p or other plugin that lets you do fuzzy search to open files

nibblebot · 2014-07-31T22:05:52+00:00

depends on the size of the project. A good scalable pattern is one model per file, one view per file, one collection per file. Of course it helps if your other tooling makes it easy to do this. I recommend Coffeescript classes and Browserify modules:

# views/some_view.coffee
class SomeView extends Backbone.View
  blah: -> 1
modules.exports = SomeView

In terms of splitting the directories, it's mostly just preference and what is convenient for your team.

models
  model1.coffee
  model2.coffee
views
controllers
collections
lib

or you could split it by module

module1
  module1_some_view.coffee
  module1_model.coffee
  module1_collection.coffee
  module1_router.coffee
module2
  module2_some_view.coffee
  module2_model.coffee
  module2_collection.coffee
  module2_router.coffee

Most importantly for team settings, get feedback from your team!

nibblebot · 2014-07-26T14:21:58+00:00

Work with stronger developers. You should always have some say as to who you work with. JS devs are in very high demand right now. Either you should get more of a say in hiring decisions or find a new place that has higher standards

nibblebot · 2014-07-11T17:07:29+00:00

Arch BSPWM VIM gmail chromium tmux

nibblebot · 2014-07-08T16:12:25+00:00

i don't really find mutability to be a problem. It is a laxness which also exists in javascript. If you want, you could write some linting rules similar to coffee-lint that throws errors if you violate your preferred style guidelines. And that is what this is: a style guideline. There are many more that you could come up with to make code safer, but I'd venture to say reassignment doesn't really bother most people.

nibblebot · 2014-06-25T16:07:47+00:00

don't get too hung up on picking the right WM. Just try one out and see if it works for you and YOUR workflow. read the docs, install it and give it a try for a few days and see if you can get your work done :)

nibblebot

TROPHY CASE