1,021 karma · joined July 14, 2011
I agree that Lazarus looks more mature, however shifting to a pure C backend would actually allow them to be more portable as I believe Lazarus uses FPC which can use a LLVM backend. While LLVM supports most modern platforms, there are lots of less popular architectures that lack LLVM support.
Personally I never liked using any basic derived language for "Real work", but not sure if that was because I was a Delphi guy.
Someone might be able to develop a method of causing this to occur by targeting a draw elsewhere, but this will likely by motherboard specific (or even entire platform specific).
It definitely means that SEV isn't going to save you if your vendors conspire against you, but unless your dealing with a determined state level actor, I doubt there is much risk to most of us. Internal actors (rogue staff) are likely to compromise in a simpler way.
However this is great research, I imagine in CPU designs that are being planned now, there will be some work to ensure the Secure processor is protected, likely by making the processor fault when SP input voltage drops. Alternatively they might be able to move some power regulation onto the processor package providing buffering against voltage manipulation.
There is such a large market for 2.5” storage that I don’t think we are going to have a large discounted sell off, unlike say DDR4 ECC DIMMs
This will almost certainly not make sense economically, but it seems a lot around RPi clustering doesn't make sense from a performance/$ perspective.
Vendor / Platform Viability - If you shut down or deprecate your platform (looking at you google!) - I loose my application. Product Limitations - I have no other option besides re-write if you choose not to support something I need after I start using your platform. Are you investing enough to support me in the future? One of the reasons many GUI web editors let you get to the code, is that it provides an escape hatch if the included tools don't work and you need to fix a problem right now. Financials - What happens if you (or whoever acquires you) decide to do an Atlassian / Oracle and let me know my next renewal is 400% higher? Processes / procedures / options - By limiting things like code access you make it harder to find ways to fit weird corporate or regulatory requirements. I might be required to keep every version of my application's code for 7 years. You might make your platform hold the last 60 version of each file. I can't guarantee my auditors that I have every version of the code.
As such I would be hesitant to do anything too significant in a No Code platform. On the other hand if the application is of minor significance (i.e. can easily be re-written) or temporary it would be acceptable.
However the value of that code will vary by language. If your doing the magic in a very niche language then it will have less value then if it uses one of the mainstream 10 or so languages. Additionally if the code depends on services that are only offered by your platform, then again it will have reduced value as the lock-in is still there.
Depending on strategy (especially around monetization) code exporting may not be viable for your platform, and the workarounds would take too long / too much resources. Now what that means is the tool needs to be SO GOOD at whatever niche it fits that it is a no brainer for me to put my concerns to the side and just try it if I need to work in that area. If your tool lets people save a heap / make money quickly while keeping quality up, it will speak a lot louder then the voice of reason worrying about long term supportability.
Maybe your writing an app that deals with some obscure data feed and feeds it into some home automation. Maybe the data comes in a format your language doesn't have a good library for right now. If its easy enough (as github and all try to make it) maybe you publish it as an experimental library for your language.
Someone else looking for that functionality for a work project sees your contribution and either contributes or forks and develops a better tested / maintained version.
If your submitting code for vanity, I can see less use, but a lot of it is public because traditionally Github would charge for private repos... people got used to just making anything that wasn't commercially sensitive open.
As for helping or hurting your career, that is very dependent on your situation and the existing team structure and culture. You can overcome most negatives that come from working remote if the organisation supports you. You can also use the flexibility to improve productivity helping the organisation more. However there is more responsibility on you doing that, and some find themselves not mature enough to make the most of it.
If your focusing on development speed to be able to add features and trying to grow quickly, then your should lean towards where existing skills are, but design it in a scale out fashion. i.e. break out your state from your http layer so you can run as many front end instances as needed to handle the load. Work on getting the data layer optimized as far as data access patterns go, and serve most of your data from a caching layer. Keep in mind that a web app like reddit spends most of its time dealing with your data layer. A Higher performance language won't fix a slow data source.
If your optimizing for efficiency (hosting and cost), then it might make more sense to start with a higher performance language, but at that point you likely want to optimize for your hosting environment. Can you make your application highly static? Can you make the pages be generated on change? i.e. new comments / posts go into a worker queue and a static HTML page is generated (possibly with some small dynamic content being pulled in from another microservice). In this architecture the web stack is dictated by your hosting environment. For AWS this would be whatever runs best in lambdas. Something like Cloudflare workers enforce JS or Web Assembly.
You also need to ask yourself if you want to develop the code or the site. If your more interested in the application then you should look for something that already exists that is close and see if you can make it work for your needs. The site likely will need a lot of work to attract a userbase, and your likely better focusing on that unless the goal is to develop the software itself.
Firstly most companies don't roll their own software, a lot of stuff is done with off the shelf products, and maybe some outsourced customization (especially in the web space). Custom software is typically only developed if 1.) there is a pressing need and 2.) there is nothing that can already fit the bill and 3.) it will result in a large enough business benefit to cover the cost.
Now there are things SMBs that do create software do to get better efficiency. Firstly teams tend to be smaller, often with a push for everyone to be "Full Stack". Originally this was Backend + Frontend, but this is often including DevOps, QA and more. Teams will often require everyone to work in every skill area at least at a junior level. Secondly there is a push in a lot of organisations for more then 38 hours of work a week in anywhere that is billing out staff.
If the address is to a large host, then they will use reaching invalid email addresses as evidence that you are not keeping to best practices. They will throttle deliverability, and possibly reject email.
If your sending to an invalid host, then your mail sending provider (if your using one) may consider you a bad customer and send you through a lower grade of outbound IP addresses.
Frequently new registrations are processed at once as batch imports from another system or from a partner. There is a need to remove these invalid email addresses pre-sending and hurting sending reputation.
AliExpress has some cost effective x79 / x99 Dual Xeon Mobo / CPU / RAM combos. System would be Sandy Bridge / Haswell. But 24 cores and 128gb of ram can go a long way and whole system cost would likely be under $2K USD. A few Sata SSDs and you could easily host a classroom on a single box.
Not Cheap if you don't have the money, but likely cheaper then a new laptop fleet.
I could imagine someone basically picking these up and collectively monetizing with ads, or other methods. Likely not suitable for a massive business, but likely able to sustain a sole operator or even a small team if operated frugally.
In outside the covid pandemic, I think you will find that there is significant international travel for breeding and show purposes. Additionally, while I am unsure of the cost in the US, in a place like Australia the quarantine costs to bring pets into the country make it something more likely to be done by wealthier migrants.
I don't know why, maybe it is that many .NET developers developed in an environment where MS provided blessed libraries for most things that was effectively bundled with the OS / Dev Tools licensing. Maybe it is that solid .NET developers end up working as consultants and thus have different vested interests. Maybe it is due to the size of organisations typically being larger and enterprisey.
Coming from the python / php / java / linux environments and dipping my toe into .NET in my current role, I believe the .NET ecosystem feels more different that any of the open source ones.
It IS a very capable war-plane for many of its roles. Much more capable then the harrier and with many capabilities that the F-16 & F-18 lack. It has different solutions to the problems it faces though.
Many of these new approaches to old problems that are arguable. Is a stealthy approach (F-35) more effective then raw manoeuvrability (F-16) in fighter vs fighter combat? Probably if the stealth can be maintained. Is high flying precisions guided weaponry as better then what an A-10 can do in close air support? Maybe? These points will be argued by airchair air marshals until we have another big war to "answer" the question.
But the F-35 has failed at being the cheap general purpose aircraft it was promised to be. It has been earmarked to replace the F-16 in its entirety, as the low end fighter to the F-22 raptor as the high end. This was one of the reasons the F-35 has a single engine. Recent moves are to make the F-35 the new high end fighter w/ a new lightweight fighter the low end that can be cheap enough to fulfil this need.
The only way this could be economical into Australia would be if it had an energy storage capacity. Someone might do the math and build a battery to be powered from this and inject into one of the grids, but longer term, if it is to supply singapore, it makes more sense to put the batteries at the singaporian end.
Or is this as simple as the offer could be modified and therefore your shafted?
However I imagine they haven't planned to reduce their brand equity like this move will do
I always thought the Australian model was better. ABC/SBS are paid out of general government coffers, people don't like it but not enough
* the model was setup while the auto makers were substantially smaller. GM / Ford couldn't hope to control the entire supply chain in the 1930s like they can now. These pre-existing businesses are able to protect their interests.
* Early cars had massive defect rates compared to modern consumer electronics. You HAD to be able to have a large number of people able to repair and maintain cars.
* Due to the value of cars, a higher proportion of damage is likely to be considered repairable over a CE device.
* Many auto parts were simpler when the model setup. Many parts did not have extensive IP protections, and were relatively easily clone-able. (i.e. you can make a mould of a part and cast other copies). Not to mention, outside a few halo proprietary technologies, companies were less litigious and protective of IP.
* Commercial operators such as Taxi and corporate fleets mean that there was a market for these 3rd party products, enough to cover R&D costs of cloning an existing part.
I think we need to enforce a compulsory licensing of IP for all parts, chips, etc after a period of non-availability or obsolescence. Price should be set at a point where 3rd party companies come in and produce generic versions, paying royalties to the owner. Allow these 3rd parties to reverse engineer the products and sell their clones if there is truly a market need.
What will likely happen is that the companies would rather license their designs to a chosen partner, in the hope of having more control over it
I think being open source is going to be required to get pyston supported by the rest of the python community. As i know for many organisations I have worked for python kind of sneaked in the back door, and without being open source, would have limited the viability. Once in it becomes easier to add support.
I think there is a good opportunity to sell support / consultancy services around performance for python, and having the engineers optimising the runtime able to be leveraged adds a lot of value. Essentially becoming for python what azul is for the jvm.