64 karma · joined November 25, 2019
Nonetheless. I am from germany and I successfully integrated sync with multiple bank accounts via aquafinance. I can pull down and automatically categorize transactions and even issue transfers.
There are more reasons i did not fully commit yet:
I have no automatic backup configured. I do not have an designated desktop-pc yet. Having all this important data on a mobile device is insecure imo. I have no _real_ usecase to apply double-checked accounting (hopefully this is the correct term).
Nonetheless, it's great. If one had a tax-guy I guess it is even more beneficial.
I think it is honorable that all these People are listed by name. And carefully summarized (apparently by hand). It shows gratitude.
Hopefully the number of votes do not get published afterwards. Otherwise the whole thing would backfire, I guess.
> I'm a web dev, so I'm not comply to web spec but chasing it, as a web dev, I'm happy about this, so I take the web spec as granted.
Okay, now I see: As a web dev you are able to make use of all these new features. I do not know about current conveniences. FWIW is that CSS should be portable across any browser/web view. And given that browsers nowadays occupy tons of memory (even though they are written in highly performant languages) I am still impressed by sciters small shipping size.
> If I'm building a app biz company, I may choose sciter. sciter is not "free" to use, I remember sciter used to tring allowed the static linking if the donation is good enough, but seems not reach the goal, which means can not get a static exe like https://github.com/wailsapp/wails .
Thank you for the recommendation!! It appears to me that his previous attempts to market his product have left a serious impression. I do remember stumbling about sciter a while ago, neglecting it as well. But I can't recall my reasoning.
> BTW, I'm sorry for the small app part, small should mean adapt or bend to sciter.
No worries, thanks for your input!!
Not every feature needs to be supported, which feature are you referring to? Also, given the use case: what is required in your opinion? How does the shift in microsofts scope translate to the efforts to sciter? What did the shift imply?
> sciter is good if you looking for make a small app which not depends too much on web spec.
Since when is it a feature to comply to "web spec"? Why should anyone continue to comply with all new requirements? And why do you feel it is required for portable desktop applications? Why not settle on some proven essentials? And why I am talking about browser now?
Hopefully you elaborate your thoughts: I am sincerly curious about your opinion.
https://openjdk.java.net/jeps/424
Anyhow - I do like the idea very much. It seems to me that it enables any solo developer to incorporate the entire jvm ecosystem. At a first glance the proposed syntax appears cumberstone, but I do not grasp everything. Do not use Clojure or CL, but Scheme.
I want to raise the following: Rust is overengineered. If these highly-intelligent contributors would settle on D, I think humanity/developer-community would archive more collaborations on essential pieces of software.
Imo a statically-typed language is required to develop maintainable code. Human communications, read documentation, is much easier to extend than compilation-restrictions of a programming language.
What are the non-fixable downsizes, which prevent serious adaptation of D? readsupuponthepostbecauseaCcomparsionwasspotted
My personal opinion is: The convenience of tooling. Currently I am developing a language agnostic language server, which aims to be integrated in unix environmets without requiring exorbitant memory (currently 8 MB + file-contents). I feel, that this is my only contribution I can submit to the community iff I suceed.
These kind of tests were complemented with a few other days, where I had to answer questions, recall stories, talk about things fascinating me, myself and my opinions, picture interpretations, sequences of digits, multiple choices and other things I cant recall. At the start of the following week, these test were rated for multiple sections of knowledge. Then, the average IQ was estimated.
What I want to say is: This is only part of the actual estimation. It is the first test, who actually reminded me of these tests.
I did not suceed in school. I did start consume drugs on purpose, getting rejected from my school and only did the necessarities. After a few years working, I did start wondering about knowledge and started to pursue studies.
If there is a topic that facinates you, such test would complement one. In the end we are all median overall.
:)
Our use cases with these solutions are kind of essential, so there are no possibilties to "give back".
Any federal agency is supposed to cover one aspect of the government services. Developing individual software, which cover national laws.
Also note that our software is almost 90% legacy code. And new solutions need to work around these quirks.
Open Source doesn't imply anything on the code. It assumes to benefit from a wide range of people (and outsiders views). Open Source projects, which would reject PRs on improving the build process will suffer contributions in the long run, risking their acceptance in the community. It should aid itself. At least this is the philosophy I proclaim myself :)
> That's the key. Many people don't bring their cars to a garage for inspection. Especially if they don't have annual maintenance intervals which typically end on the same month as the HU intervals.
Annual intervals ensure an easy TÜV inspection, but it is differs entirely from the raised point. You can hire a garage to present your car - no need for an annual maintenance contract. No need for intervention by the car manufacture. And you shortend the quotation: Why are you explicitly calling german brands out for: "the average german branded car owner who signed an annual maintenance contract" and why are you omitting my point, that this can be done with any brand and any age of vehicle? I would claim that the luxury brands have _less_ annual maintenance contracts by private households. You need to provide sources for your claims - I just pointed out, that there is no correlation with your claim and it is a biased assumption.
> > The price for the check is fixed. You only fail the check, if there are crucial safety issues or oil leaks
> I don't doubt that. The question is whether the dealership will inspect your car before your official inspection or not.
Any garage can inspect your car - regardless of age. Your opinion is only proven if tesla owners hire less garages then any other brand. And then the age of the car is still neglected.
> > You do also insult any inspector (DEKRA, GTU or TÜV) by promoting such implications.
> ??? I am only saying that dealerships are inspecting cars before official inspector sees them, and the rate of pre-inspected cars differs from brand to brand. I don't blame DEKRA, GTU or TÜV for faulty inspections. I blame them for not disclosing the bias in their statistics.
Inspectors treat any vehicle the same. That means that any garage is able to ensure a successful inspection. There is no dependency on the dealership. Additionally, the owner is responsible for preparing the car.
Since we are referring to fairly new cars: Depending on the kind of purchase the owner _is required_ to present his car at a garage in an interval. Otherwise he will loose his warranty or additional insurances.
And my personal opinion: Anybody who repaired any car on its own will agree: teslas quality is ridicolous cheap.
Tesla has dealerships, but this is irrelevant. You are referring to garages, which can be included within a dealership. If you bought a car, you can opt into these contracts. Otherwise you can become a customer of any garage. All cars were compared. There are still 10% of teslas, who can not successfuly survive the initial inspection without additional maintenance.
> When you own something like a BMW, you typically don't drive the car to the inspection yourself. Especially not if it's a leased or company car. Instead, you bring your car to the dealership (or they will pick it up), they inspect the car, fix any issues they encounter and only then bring in an official inspector for the actual inspection. This way, the inspector will hardly find any issues. Also, dealerships typically don't chose TÜV, but one of their competitors that do the inspection at the dealership.
This is valid for any car, regardless of its age or brand, if a garage presents your vehicle for inspection. No need to refer to "german car brands". Also competitors need to respect the same criterias.
> TÜV is where people go who want to save money by skipping the dealership.
The price for the check is fixed. You only fail the check, if there are crucial safety issues or oil leaks. The majority of car owners is thankful for a safety hint from the inspector.
> Most people who do this drive cheaper cars. That's why cheap cars are always having much worse numbers in these statistics.
That is an assumption.
> They are alternative statistics, like ADAC's (Germany's equivalent to AAA), but they all have the same problem. There are no good statistics for German cars. They all favour expensive German brands because those who the statistics will never see a broken car.
This is a biased assumption.
> The dealerships will always take care of that. I'd rather trust US-based Consumer Reports than TÜV or ADAC statistics.
The dealership only takes care of problems iff you either signed an maintenance contract and additional insurance, the issue needs to be solved due to warranty or you accept the charges neccessary to fix the problems.
It simply _is_ the case that tesla has a lower quality then any other europe car brand. Dacia is on the same level as tesla in terms of haptics - but their internas (chassis, engine, bearings..., etc.) are siblings of mature brands.
The TÜV is responsible for checking for safety - Inspectors will get their license permanently revoked if they did not spot an serious issue. I would trust TÜV over any american report.
When an accident happens and a certain money cap is reached, insurances will investigate and escalate to anybody. The TÜV will not prefer any car brand and take these risks.
You do also insult any inspector (DEKRA, GTU or TÜV) by promoting such implications.
Is crucial for my personal workflow and one of the only bindings i require.
I use it in conjunction with
`nnoremap - :Explore<cr>` Which opens the best directory navigator in existence (actually dired should be named here)
This changes the game dramatically.
Read about :ls and :b
It did persist the state after closing the tab. Admittedly, I did not check the site for cookies.
Does this open up my browsers to execute code in the background, even after closing the tab? Does it imply an additional threat to my personal privacy?
Nice work presenting this feature, though!
One of these rules is (hopefully), if i purchase a hardware gadget, all of its capabilities are my possession. Restricting the access on purpose is frault. Epic's case is just a consequence of the missing regulations when providing software AND hardware.
long live the EU and their friends.
All people who are important to me migrated. Some refused for a long time for no reason, but in the end installed a separate app alongside WA.
But I get your position: Judging by the amount of unfair usability and amount of third parties involved in any co.uk-domain, it appears to me that the common folk gives a shit about it over there. However, I wont get any site a visit who does the above. There are alternatives to gain information.
I am proud of my nation: We shifted our values - we rated our ecosystem higher than competitive advantages.
Do not worry about the size of your app. Managing decoupled apps is way more annoying then conciseley written ones. And by the phrasing of your question I assume you are projecting the complexity of the codebase to the capabilities of the app.
My piece of advice is the following: When developing for mobile modularize the functionalities by screens and aim for a strong coupling within them. Even when the functionalities are growing (proportional to the success of the app, that is), you will not often see too many similiarities between them and the redundancy is factored out easily.
Only when starting to develop a larger app which shares multiple screens across it could make sense to bundle differently. In this case, you want to structure the codebase by your tests. Most of the time, reusing a screen creates plenty pitfalls, which can simply be avoided by not reusing.
Due to grouping the functionalities by screens, issues will mostlikely not be related to eachother. Also, in my experience, libraries introduce more issues then solving, so trying to keep the app barebone will often result in a smaller download size and a more robust app.
When applying these thoughts properly a larger app could look like the telegram client! https://telegram.org/apps#sourcecode