darthbanane
Joined 9 years ago
Joined 9 years ago
This thing will run android on a mediatek chip, it's not a purchase once and done type thing like the keyboard attachment.
The leadership behind this project is f(x)tec. While they're not outright scammers they have a TERRIBLE track record in delivering products like this. Just look up the old fxtec community forums or the indiegogo pages for the pro1 / pro1x.
It's just data points but so far the modus operandi was to take pre-order money and then take years to deliver a bad product with no aftermarket support. There were always new excuses about what happened (shipping company stole our stuff! chip reseller scammed us! etc) but no transparency. The reality seems to be they ran out of money and instead of being upfront about it kept making up new stories why nothing was happening. The few devices they have shipped are basically unusable unless you're going to mod the hard- and software yourself (no security updates, issues in antenna design, outdated hardware by the time it ships, keyboard quality issues, you name it).
If you're interested in the device I implore you to wait until you can buy it upfront (ideally in a physical store) and return it at your convenience.
I thought I needed a keyboard too, but when everything is designed for a slab screen and your "productivity" phone randomly shuts down or has no reception in a major area, you gotta think about what productivity really means.
If you inject the bean and call the method you will get caching (because you are using the proxy). If you call the method from within the bean itself however you're not using the proxy and you won't get caching.
It's stuff like this on steroids when you start mixing annotations that makes it really difficult to reason about the code.
I mean sure, if it keeps things fresh and keeps you moving it's better than nothing but that's not a good structure if you want to progress past a year of training or do anything serious.
Literally just doing a random program like the reddit recommended BWF routine is vastly superior and doesn't require chatgpt or serverless or anything..
In several occasions it has produced code that took me longer to fix than just reading the documentation and in almost all of those cases it couldn't help me find the issue and I actually had to read the documentation anyway (it took just seconds to pinpoint the missing clue).
Something it seems really good at is unix commands (regexes, awk expressions, pipes and bash intricacies) so I do use it a fair bit for that.
The screenshot says just amend the commit and all's good
The message says to remove the secret from the commit but the actual action to take would be to rotate the secret since it's been exposed to github, no?
There's a shared secret you can use to verify the payment when they callback to you after payment, and their HPP is skinnable.
[1] https://docs.adyen.com/developers/api-reference/hosted-payme...