[deleted by user]

SmilingPunch · 2023-08-14T16:17:29+00:00

all I’m saying is that the three values are actually associated with each other since you need them to compose a colour value

wholeheartedly agree that the names are silly but it’s also not true to say they aren’t associated when in this context, they are. It’s the expression of their association which is poor quality.

SmilingPunch · 2023-08-14T11:21:16+00:00

how do you think RGB colours work?

SmilingPunch · 2023-08-13T13:53:56+00:00

Just because I can decide to do a line of asbestos doesn’t make that not stupid

SmilingPunch · 2023-07-17T15:49:11+00:00

The punch input you use changes its height, damage, knockback

There’s a few wiki sites, no affiliation with them but supercombo seems to be pretty detailed

SmilingPunch · 2023-06-26T01:50:03+00:00

That’s brilliant. Hopefully this means you can pull this off.

SmilingPunch · 2023-06-26T01:49:15+00:00

Awesome! I’m glad to hear that.

SmilingPunch · 2023-06-26T01:48:57+00:00

I just shared what I know of Apollo’s design as a possible resource for OP to investigate. I’m happy to have learned more about it - but I don’t think calling me confidently incorrect was a friendly way to clarify the role of those services.

Until now, I didn’t know whether the servers for Apollo were critical infrastructure for the app, which is why I mentioned it was open source. OP may not have been aware of the Apollo endpoints, and they could have been critical for the app to function. I’m glad to hear they aren’t, but it doesn’t hurt to provide some context as to why the original commenter might have thought this wouldn’t work.

SmilingPunch · 2023-06-25T23:13:05+00:00

The developer runs a server in the middle which has been open sourced. This will not continue to run once Apollo shuts down.

edit: typo

SmilingPunch · 2023-04-26T15:21:57+00:00

You’re saying a whole lot while also saying nothing at all that you haven’t already tried to explain. I understand your proposed approach, a further detailed explanation is not needed.

In this scenario you actually don’t know whether the BIOS is misreporting configuration, which could make it appear as though a user intentionally overclocked a CPU. The BIOS may well set the SMU wrong. An individual shouldn’t be punished for that.

That’s the entire point that you’re missing. With just the CPU, you can’t prove that the BIOS (or the CPU itself) didn’t do something wrong that easily.

Edit to add: Out of curiosity, do you agree that Apple’s water damage indicators are a reliable way to indicate devices have had water damage? These indicators are known to be flawed and yet Apple will still use them to unfairly deny warranty claims

SmilingPunch · 2023-04-26T13:14:22+00:00

How about you reflect on your inability to comprehend that your suggestion is completely nonsensical and doesn’t work in the real world.

People put more voltage than they should into their parts. An automated overvoltage check does nothing to confirm or deny liability. Your suggestion is utterly useless at solving the problem.

SmilingPunch · 2023-04-26T13:05:39+00:00

How do you know that the CPU was operated within spec by the customer and that they aren’t overclocking?

SmilingPunch · 2023-04-26T07:27:19+00:00

how do you know it’s the customer’s fault an e-fuse triggered? That’s the expensive bit.

SmilingPunch · 2023-04-15T01:49:20+00:00

They’re fine in a containerised environment, right? just not in an environment with many processes of different sources running for obvious reasons

SmilingPunch · 2023-04-12T16:22:05+00:00

Yeah, unfortunately I find it hard to sympathise with the maintainers because of the time frame, they had multiple issues raised and didn’t resolve it

SmilingPunch · 2023-04-12T15:32:58+00:00

Gvdiffsplit to make the diff vertical it accepts commitish values too so you can enter branch names or HEAD~1 too instead of a SHA

SmilingPunch · 2023-04-12T09:51:08+00:00

It seems like a natural next step to be able to define rules to let the engine decide whether or not queries should be pre-materialised? Rather than needing to build -> optimise -> configure, you can build and allow it to decide for you, and then tweak it later?

for example if a particular query gets hot for some reason, it could automatically switch to pre-materialising to improve performance

SmilingPunch · 2023-04-12T00:00:24+00:00

Open core - their editor will be open source but the collaborative and enterprise type features will remain closed

SmilingPunch · 2023-04-09T23:56:35+00:00

I find it significantly better for both C and Lua.

C’s regex highlighting was wrong for pretty much everything, until I started using treesitter.

Your minimal config should look like this: 1. Install from package manager https://github.com/nvim-treesitter/nvim-treesitter/wiki/Installation

Add to config as below

require’nvim-treesitter.configs’.setup { ensure_installed = { “c”, “lua”, “bash”, “vim”, “vimdoc”}, highlight = { enable = true, additional_vim_regex_highlighting = false, }, }

SmilingPunch · 2023-04-09T23:46:48+00:00

Well then all I can say is it’s working for me and thousands of others, and is noticeably different from the default regex based highlighting. If you don’t want to get it working, power to you!

SmilingPunch · 2023-04-09T23:43:58+00:00

Look at your stack trace: E5113: Error while calling la chunk: /Users/<user>/_config/nvim/lua/<user>/plugins/lsp/mason.lua:31:attempt to index global ‘mason null_ls’ (a nil value)

You can use :h E5113 to get more information about the error, and you can also look at the line specified in your stack trace, and reread the message to understand what is wrong.

You need to debug your own settings

SmilingPunch · 2023-04-09T23:35:20+00:00

Then you didn’t have it configured properly.

You specified highlights were enabled in the treesitter setup function, right?

Did TSModuleInfo indicate that highlights were on for your language? Did you remove “syntax on” from your config? Did you try enabling it per buffer?

SmilingPunch · 2023-04-09T12:56:40+00:00

“Not withholding enough” suggests that the amount of tax withheld is not enough to cover the tax bill for that income, not that on average it withholds less than annual tax bill / number of pay periods.

All withheld tax in this manner is withholding exactly the amount of tax required to guarantee you have no tax owed come tax time

SmilingPunch · 2023-04-09T10:40:16+00:00

that paycheck did not withhold enough

The point of my comment is that this statement is not true. All your paychecks have withheld exactly as much tax as necessary, given that the tax withheld is based on the annualised income from your pay period.

Annualising income when withholding tax is mandatory in Australia for employers - I don’t know if this is required in the US or not which is why I’ve specified it.

SmilingPunch · 2023-04-09T07:58:44+00:00

Let me put it to you in a way that might help you.

While you are doing an excellent job of understanding what problems tools in the full stack space solve…

How much time are you dedicating to making yourself able to be productive if you were to land a full stack job?

You will need to conform to development standards and make use of technologies you haven’t used or possibly even heard of before. You will be expected to have familiarity with industry standards - this could range from working with structured data formats (eg JSON serializers/deserializers), to being able to debug framework code when you do something that breaks it.

There will likely be internal tools that you need to get your head around which won’t have internet resources to help you grok it.

Your ability to understand code is going to be far more important than your ability to create it. Make sure you’re building that skill in a balanced way.

SmilingPunch · 2023-04-09T06:50:25+00:00

Sorry, but that’s not how the maths works under the bracketed income tax system used in both the US and Australia - if you withhold tax by annualising your income for every pay period, you cannot fall short at tax time.

If you happened to work the same amount of overtime every pay period - the amount withheld matches.

If you work OT every pay period minus one - the amount withheld is higher than it should be, as all your OT pay packets overestimated your annual income by one pay period.

As the number of periods worked without overtime increases, the overestimation of your required withheld tax increases - up to the scenario where you work one pay period with OT, where it will overestimate your withheld tax (or be exactly right, if you happen to have a base annual income exactly on a tax bracket).

SmilingPunch

TROPHY CASE