|
I just manage my - and my clients' sites - via Plesk and that (generally) has a LetsEncrypt plugin installed by default. 2 mouse clicks to setup initially, then forget about.
I agree, mucking about purchasing and installing certs was a pain. Thankfully my needs are fully met by LetsEncrypt, and it's unlikely I'll have to go through the rigmarole of more "extensive" certification again.
|
|
|
|
|
I have never really understood this certificate thing.
To me, this is just a level of unnecessary complication for everybody : the ones issuing it, the ones installing it, and the ones having to use them. I really wonder if it is worth it, all in all.
|
|
|
|
|
Something about making sure the data you send through a website is properly encrypted and unreadable to prying eyes, I don't know the specifics.
Some very smart security people have thought about it and came up with this solution.
On the other hand, JavaScript is also a widely adopted technology, so maybe certificates are just as bad except I can't really tell because I don't know half as much about certificates as I know about JavaScript.
|
|
|
|
|
God, please God, don't make me do web work. 
Charlie Gilley
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
Has never been more appropriate.
|
|
|
|
|
I used to do desktop development (WinForms) and it had its flaws.
Updating a web app is far more easy, as are automated releases.
With a web site, you simply deploy and all your users have the newest version.
Handling secrets is far more easy, for example connection strings.
They live on a server and users simply don't have access.
And, well, those are pretty much all the pro's 
Although I love .NET (Core) and going back to .NET Framework, even the latest version, now feels archaic to me
Of course that doesn't have to be a problem anymore with WinForms being in .NET 5+.
|
|
|
|
|
Sander Rossel wrote: They live on a server and users simply don't have access.
That could be discussed about... 
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
I hate you. You are making a good argument for maybe the tech has progressed. I need more drugs 
My wife was a web developer in the wild days... before 2000. Note pad was your friend. So... I had to deal with 404 errors, backend server weirdness. It was maddening.
But I have this app I need to develop. And it seems everything is ROARING to "let's put it on the cloud, what could go wrong?" Years ago I went through OLE/ActiveX/COM/COM+ and there might have been something else - damn Microsoft clowns.
So when I see .net times 13, azure, this that and the other... I have tools from Microsoft that won't work properly, it's a complete charlie foxtrot.
I am afraid.
Charlie Gilley
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
Has never been more appropriate.
|
|
|
|
|
|
And if you look at the comments, you see that the first one refers precisely to this.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
Not only that, but this is a comic from almost 5 years ago.
Are you regression-testing?
|
|
|
|
|
dandy72 wrote: this is a comic from almost 5 years ago.
I've read through the entire Dilbert oeuvre (over the past couple of years) and I'm just 5 years out from finishing them all.
Yes, I'm serious.
Dailies started on April 16, 1989 and I've read through all those years so far.
Yes, I believe my brain has been altered from reading them.
|
|
|
|
|
Well, I've been reading it daily for years, and I'm sure I've missed out on more than the first 5 years. If it's a competition, you win...
|
|
|
|
|
0.33 amps at my bench. That's what the circuit I'm working on is drawing off my USB port.
Just 36 of these and I'd have the same draw as a relatively powerful vacuum cleaner.
This is bad, because the whole thing needs to run on a battery. I wish it didn't.
It's got a large (for its class) display like the size of the largest display you could find for any phone. (it would be a big phone). I think that's where most of the draw is coming from. Then there's the bluetooth (since I don't have a button for it it's always on) which takes at least .10 amps by itself.
But my client is like, "don't worry about it right now"
I don't know how to explain to him just how expensive it will be to worry about it later.
I really don't want to have to remodel my entire codebase a month (or less) from now.
It's not about the extra work - I get paid one way or another - but it's the high probability of breakage. With IoT code, it can't always afford to be written in such a way that it's compartmentalized and abstracted out, so the blast radius of a design change tends to be pretty large.
I don't like being in situations where I can't communicate the consequences of a hasty decision effectively to someone that needs to hear it, but this is compounded with IoT stuff because of the way the code has to be written.
It's a strange landscape for me. All of this IoT dev is relatively new to me and I'm still learning the pitfalls.
Real programmers use butterflies
|
|
|
|
|
0.33 A at what I assume is 5V, 36 of those would equal what I call a very weak vacuum cleaner.
Actually doubt you can even clean your keyboard at 60W.
|
|
|
|
|
Fair enough. I don't usually do electronics math
Real programmers use butterflies
|
|
|
|
|
No worries, about the math that is.
Out of curiosity, what batteries are you going to use? And how long do they need to last?
2 W is still quite a drain on the batteries.
A regular 18650 lithium battery has about 9 Wh and would last up to 4 hours assuming 90% efficiency in the regulator.
|
|
|
|
|
We haven't decided on an exact model yet because it's still being v1 prototyped and the size of battery we get depends heavily on the physical dimensions of the final widget. the first prototype is USB powered only.
So it's possible it won't be an issue. 4 hours isn't terrible for what this is. Thanks. I'll run that by my client. If it saves me a lot of hassle making it save power I wouldn't mind. 
Real programmers use butterflies
|
|
|
|
|
train wreck approaching....
software is one thing, power requirements are entirely another. "Quote: But my client is like, "don't worry about it right now"
"
get that in writing. Sounds like a good client be blunt and upfront. I think that comes easy for you
Charlie Gilley
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
Has never been more appropriate.
|
|
|
|
|
charlieg wrote: get that in writing
Wise words indeed. 
Quote: software is one thing, power requirements are entirely another
Many times those are somewhat intertwined, given low power 'sleep' modes available on most MCUs.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
The software has a ton to do with the power draw, because I control when everything is on or off
Real programmers use butterflies
|
|
|
|
|
IKWYM. Back in the 80's I worked on a financial calculator which used a NEC V20 (CMOS 8088) and had a 4x20 line LCD. We arranged that it spent most of its time sleeping, only waking up when a key was pressed and caused an interrupt. This allowed it to run for days on the then common NiCd battery packs we were using. If we didn't put it to sleep, it ran for about an hour or so, tops.
|
|
|
|
|
honey the codewitch wrote: it can't always afford to be written in such a way that it's compartmentalized and abstracted out, so the blast radius of a design change tends to be pretty large.
Upvoted for eloquence
«The mind is not a vessel to be filled but a fire to be kindled» Plutarch
|
|
|
|
|
Whenever anyone tells you not to worry you should insist that they explain why you shouldn't worry. If they can't explain why then they are either hiding something from you or they are drunk on a culture of not worrying when really they should. Don't let them keep you in the dark because that will cause you a lot of worry. If disaster strikes then saying that they told you not to worry about it is going to sound a bit lame.
|
|
|
|
|
honey the codewitch wrote: the blast radius of a design change tends to be pretty large.
I laughed out loud when I read this snippet. I want to use it the next time my boss asks for something to be done in a questionable way.
|
|
|
|
|
Look at your power supply design. Consider replacing LDOs with DC-DC converters.
Don't forget electrical emissions requirements if you make this change. Buck converters radiate out their inputs.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
