So they aren't bricked then?
2,201 karma · joined August 28, 2015
No, the complaint is about the "offering" in the first place. People don't want your shit forced in front of them. The fact that you are incapable of realizing this on your own is hilarious.
So do they have to order new routers every time you do this? Hopefully after you have destroyed all of their routers, they will eventually buy new ones that are actually compatible with IPv6 so just keep doing it. /s
But granted your typical charity has no idea of what the jargon is in the security (or even broader technical) field, and so "red teaming" is a vague enough phrase that could mean anything.
The Wikipedia article was also a good read.
> The same issue plagues domesticated cats, they don’t need to hunt for food since they have an abundance at home so instead without risk of starvation they are free to hunt all birds in the territory for fun.
Please could you help me understand.
- If they don't _need_ to hunt for food, the frequency of hunting birds should go down (even if they still do it for fun sometimes)
- If they don't need to take risks to get food, why would they then take those same risks now for the purpose of entertainment? (That cancels out any meaning of there no longer being any risk in killing birds, so why mention it at all?)
My understanding is that you are implying that cats not having to kill birds out of necessity leading to them now being able to do it for fun is a bad thing. Is that correct? And if so, I don't follow that logic because of my above two points.
> That’s what negative prompt is for.
This is what I mean by it "not understanding negations" You need whole separate prompt, just to say you want e.g. "ramen without egg" instead of just saying it in a single prompt that it understands.
Try "ramen without egg" or "ramen with no egg" and it will show ramen WITH egg.
Or "man without striped shirt" will give "man WITH striped shirt"
[0] https://archlinux.org/packages/extra/x86_64/xorg-xlsclients/
You can do the exact same thing with code. You can still output reports and diagrams, and literally anything the "customer/user" wants.
> I could have done a database with my wife's sewing patterns collection...
Your example is a good one. I didn't think of images.
> It was done in 2-3 hours, and she got exactly what she wanted.
Fair enough. A spreadsheet was probably the right tool for the job in this case. But if she ever wanted more features, and the complexity increased, I don't know if it still would be.
> I worked in a place where both the input and output was spreadsheets, and the users were spreadsheet users.
Okay, but should they have been? Would custom software not have been the better solution?
> a lot of the business logic (e.g. initial data validation, final presentation of the results) lived on the spreadsheets themselves.
When I think of "business logic", "data validation", and "final presentation", a spreadsheet is one of the last tools I'd reach for.
> Another interesting one is data-to-visual time. Unless you happen to be proficient in a particular area of programming (e.g. front programming with proficiency in something like D3, or R programmer) getting decent graphs out of data is a chore when going the programming route. With spreadsheets, you put the columns and get the graphs essentially for free.
I also disagree with this. I am very much a back-end developer. But using something like GNUplot or a library like matplotlib is pretty easy for outputting a nice looking graph from tabular data.
> To me spreadsheets are just another tool in the toolbox; they are appropriate for some tasks. They can definitely be misused and abused. Knowing which occasion is which is where experience comes in.
I agree with this. But I guess the difference is I can think of almost no circumstances where it's the better tool for a coder.
> Conversely, even if you are a coder, classic spreadsheets are extremely useful for any type of ad-hoc reproducible calculation
Again, I still feel like code is the ideal solution to "ad-hoc reproducible calculations"
> the point is that you can cross-reference cell values and copy/paste with relative cell positions to create large calculation tables/matrices, then update base values and perform "what-if" analyses, etc. etc.
I still don't see how you can't do that with code, nor what the spreadsheet is doing that code can't.
> I've used it for all kinds of reports apart from financials (benchmarks, construction/project planning, even a Tic Tac Toe game in school out of boredom).
Sure. It has been proven that excel is Turing complete. But I'd rather use a programming language (a tool that was literally designed for the purpose of writing code), than a clunky spreadsheet. Both can get the job done, I never denied that. But I still don't see the value that the spreadsheet brings over custom code written to solve the exact same problem.
I've never really had a problem entering data into CSV file or database, but I will concede that it is even easier to enter the data via a spreadsheet.
However, I still think custom software (with proper UI for input if necessary) is the better way of dealing with the actual solution that a spreadsheet is ultimately trying to solve.
I know. Most people don't know how to code, thus they are forced to use spreadsheets as I already mentioned.
> spreadsheets have a lower threshold to pure data
I'm not sure what you mean here. That it is easier for the average human to work with data using a spreadsheet compared to code?
Sure, as already mentioned. Most people don't know how to code.
But what I'm getting at is that a spreadsheet is the poor mans code.
And if you audience is coders (not the whole world), then why go for the worse option?
In my opinion: if you can use vim, you can probably code, or at least figure it out without too much trouble. If you can code, then you don't need a spreadsheet. You can just write a program to crunch the numbers, or produce a report etc.
Excel is so popular, because it is a way for non-coders to crunch a bunch of numbers in a relatively easy way. And the best way to get the answers that they are getting out of the spreadsheet is to write code. But because they can't code, they have to use a spreadsheet.
If there is a use case for spreadsheets that is not better served by some real code, I'm interested to hear what it is.
You could also make the "speed" argument (just a quick calculation) for spreadsheets, but in that case, I find something like a python REPL just as quick, and still better anyway.
AI alone has had many and this is just another one of them. https://en.wikipedia.org/wiki/AI_winter
Just because we have made progress since the last one doesn't mean that _this_ time it will be magically different.
So what makes you think this will be any different?
Keep in mind that each hype cycle was started by a leap in progress, so you can't say this time it is different because we made a big leap in progress.
I guess I'm surprised that such a crucial feature isn't standard in everything if you can't even properly display a common language like Arabic without it.
> Manage timelines, allocate resources, and monitor deliverables for your projects.
Yes but how? Some screenshots or a video might help. Even some more detailed text.
I'm not going to compile every random project just to see a "quick" overview of how it actually works.
Why share it now that it's way too late?